vuln-assessment-methodology SKILL.md skillA
vuln-assessment-methodology from dreadnode/capabilities is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dreadnode/capabilities/vuln-assessment-methodology@git:20260606.4746947Pins git:20260606.4746947 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/vuln-assessment-methodology/skills/vuln-assessment-methodology/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260606.4746947, committed Jun 6, 2026
- First version recorded
- Jun 5, 2026
- Size
- 7,873 bytes
- Repository stars
- 22
- License
- MIT
Load when performing vulnerability assessment in any domain. Enforces source-to-sink tracing, disprove-first analysis, threat-model-aware severity, confidence classification, attack chain analysis, CWE mapping, remediation quality, root-cause deduplication, scope documentation, and opt-in PoC validation. Prevents false positives and severity inflation.
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
# Vulnerability Assessment Methodology **The goal is accurate, honest findings — not volume.** One correctly-assessed finding is worth more than ten inflated ones. ## Hard Rules ### 1. NEVER report a sink without tracing the full data flow Seeing a dangerous function is NOT a finding. Trace from **attacker-controlled source** through every transformation to the sink. If sanitization exists, the finding is invalid unless you demonstrate a specific bypass. **Before reporting, answer:** - What is the attacker-controlled input? - What transformations does it undergo? - Does any transformation neutralize the attack? - Can you construct a concrete input that reaches the sink? ### 2. Try to DISPROVE your finding before reporting it Actively look for evidence it is NOT exploitable. Read the FULL function. Look for validation, input filtering, authorization checks, type constraints, config gates. If you find defensive code, demonstrate a bypass or retract. ### 3. Severity must reflect the ACTUAL threat model Assign severity by source, access, and context — not vulnerability class name. | Source of dangerous input | Access required | Severity | |---|---|---| …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/vuln-assessment-methodology@sha256:b6d1b45a0f66392eThe line at the top of this page pins the label git:20260606.4746947, 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_p4eqqcb4a7mddgbv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 5, 2026 and Jun 6, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.4746947 latest | 2026-06-06 | 4746947 | 7,873 B | A | view · diff |
| git:20260606.d4b92a2 | 2026-06-06 | d4b92a2 | 7,746 B | A | view · diff |
| git:20260606.6e4aac6 | 2026-06-06 | 6e4aac6 | 7,588 B | A | view · diff |
| git:20260605.9818bab | 2026-06-05 | 9818bab | 4,695 B | A | view · diff |
| git:20260605.b0755a3 | 2026-06-05 | b0755a3 | 9,280 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 (7873 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
dreadnode/capabilities · 22 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p4eqqcb4a7mddgbv GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/vuln-assessment-methodology GET https://markdownregistry.com/api/v1/blob/b6d1b45a0f66392e86490862b575694fd3ad68e7d60cf9cf4c16afd371fb60e8
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.