writing-vuln-reports SKILL.md skillA
writing-vuln-reports from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/writing-vuln-reports@git:20260818.ed96156Pins git:20260818.ed96156 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/writing-vuln-reports/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260818.ed96156, committed Aug 18, 2026
- First version recorded
- Aug 16, 2026
- Size
- 6,252 bytes
- Repository stars
- 26
- License
- MIT
Turn a confirmed finding into a clear, reproducible vulnerability report a maintainer or triager can act on without a back-and-forth. Use after a finding is confirmed (via the finding schema) and you need a writeup - a bug-bounty submission, a security advisory, an internal ticket, or a disclosure email. Covers the report structure that gets findings fixed, writing a reproduction that actually reproduces, justifying severity honestly, and the disclosure etiquette that keeps you in bounds.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Writing vulnerability reports A finding that isn't clearly reported doesn't get fixed. The job of a report is to move a specific defect from your head into the maintainer's, with enough proof that they can reproduce it in minutes and enough impact that they prioritize it, and nothing else. This skill turns a schema-shaped finding into that report. ## When to use - A finding is `confirmed` (see [FINDING-SCHEMA.md](../../FINDING-SCHEMA.md)) and you're writing it up for a human: bounty submission, advisory, ticket, email. - You have several findings and need consistent, triager-friendly writeups. ## Scope check Only report findings from authorized testing, to the party entitled to receive them (the program's channel, the maintainer's security contact, your client). Don't disclose someone else's data or a third party's system you weren't scoped to touch. When in doubt about the channel, ask before sending - a report is outward-facing and hard to unsend. ## The structure that gets findings fixed Lead with impact, prove it fast, make the fix obvious. Sections: 1. **Title** - the specific defect and where. "IDOR in `admin_bulk_delete` lets …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/writing-vuln-reports@sha256:7f35a8de0592d619The line at the top of this page pins the label git:20260818.ed96156, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_oh7hej22dmgm3zqq)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 16, 2026 and Aug 18, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260818.ed96156 latest | 2026-08-18 | ed96156 | 6,252 B | A | view · diff |
| git:20260816.faa9c07 | 2026-08-16 | faa9c07 | 6,251 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6252 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oh7hej22dmgm3zqq GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/writing-vuln-reports GET https://markdownregistry.com/api/v1/blob/7f35a8de0592d619f24e9cb5db08cc3f12a765ecb4bd78a4b3c994b5491486bc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.