recursive-code-analysis SKILL.md skillA
recursive-code-analysis 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/recursive-code-analysis@git:20260728.71566e8Pins git:20260728.71566e8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/analysis-ledger/skills/recursive-code-analysis/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260728.71566e8, committed Jul 28, 2026
- Size
- 6,407 bytes
- Repository stars
- 22
- License
- MIT
Use when code analysis, vulnerability research, or architecture mapping needs a durable worklist that can resume across context or session boundaries.
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
# Recursive code analysis Traverse code through an explicit durable frontier. Store conclusions and remaining work in Analysis Ledger items; do not rely on conversation history as the coverage record. ## Start or resume 1. Resolve the canonical repository path, normalized objective, and immutable revision. Use the Git commit when available; otherwise compute and record a source fingerprint. Derive `run_key` as the first 24 lowercase hex characters of SHA-256 over `repository + "\n" + revision + "\n" + objective`. 2. Call `search_items` with the computed `run_key` and `item_type="analysis_run"` before creating one. Read candidates and resume only an exact `run_key`/objective/repository/revision match; never mix revisions. 3. Create a run with `report_item(item_type="analysis_run")`. Use a stable, project-unique ref prefixed with `analysis-`. 4. Survey structure with `glob`, `grep`, and `filemap` when available. Seed three to ten high-value targets, not every file. Favor entry points, sinks, trust boundaries, dispatchers, and nodes that gate deeper code. 5. Link each target to the run with `part_of`; link discovered children from …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/recursive-code-analysis@sha256:16d68b0b6db77cceThe line at the top of this page pins the label git:20260728.71566e8, 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_2a6zt4i75nfujjuj)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 28, 2026.
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 (6407 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_2a6zt4i75nfujjuj GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/recursive-code-analysis GET https://markdownregistry.com/api/v1/blob/16d68b0b6db77cce6d2cbc75218f563bf59eecb948347bd452f836ab89fb5be8
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.