hunting-bugs-with-a-code-graph SKILL.md skillA
hunting-bugs-with-a-code-graph 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/hunting-bugs-with-a-code-graph@git:20260816.faa9c07Pins git:20260816.faa9c07 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/hunting-bugs-with-a-code-graph/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260816.faa9c07, committed Aug 16, 2026
- Size
- 6,083 bytes
- Repository stars
- 26
- License
- MIT
Hunt security bugs across a whole codebase by reasoning over its structure (call graph and dataflow) instead of grepping for keywords. Use when you have source access to an authorized target (your own code, an OSS project, or an in-scope engagement) and want systematic coverage of a bug taxonomy rather than a single hunch; when the question is "who calls this, what reaches this sink, which peer function is unguarded." Orients on an unfamiliar codebase, enumerates the full bug taxonomy before…
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
# Hunting bugs with a code graph Grep finds strings; it misses the caller behind a rename, an alias, or an import indirection, and it cannot answer "what can flow into this argument." Reasoning over a codebase's *structure* - its call graph and dataflow - can. This skill is the master loop for a source-level hunt. Two companions go deeper on single moves: `adjudicating-taint-paths` (lead → decided finding) and `auditing-guard-gaps` (the unguarded peer of a guarded function). ## When to use - You have source and want *coverage*, not a one-off keyword search. - You're cold on an unfamiliar codebase and need to find where input arrives. - You want to work a bug *taxonomy* systematically and prove what you ruled out. ## Scope check (do this first) Only run on code you're authorized to analyze: your own, an OSS project you contribute to, a CTF, or an engagement where source review is in scope. If you can't name why you're allowed to read this source, stop. ## The loop 1. **Index the target.** Build a structural index of the source tree. It is a *snapshot* - re-index whenever the code changes in a way that matters, or you will adjudicate against stale structure. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/hunting-bugs-with-a-code-graph@sha256:a0e429ec31574dd4The line at the top of this page pins the label git:20260816.faa9c07, 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_5frf7eazhldfhy2d)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 16, 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 (6083 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_5frf7eazhldfhy2d GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/hunting-bugs-with-a-code-graph GET https://markdownregistry.com/api/v1/blob/a0e429ec31574dd4451991ef0ed90d4ee7c275812ec010f6ca98401d5faac65f
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.