Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add HuginnIndustries/CodeCartographer --skill defect-scangit clone --depth 1 https://github.com/HuginnIndustries/CodeCartographerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/huginnindustries/codecartographer/defect-scan)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/defect-scan"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/defect-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/defect-scan"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/defect-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.01920 |
| Opus 5.5 | $0.00025 | $0.00768 |
| Sonnet 5.5 | $0.00012 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
scan-for-defects scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan For Defects
This phase runs six sequential analysis passes, each focused on one category of defect. Read and execute the passes in the order listed below. Do not try to cover all categories at once — complete each pass before starting the next.
The source code to analyze is in the parent directory (../ relative to .codecarto/). This is the repository root.
Prerequisites
Required: Read findings/architecture/architecture-map.md before starting. You need the layer map, public surfaces, and concurrency model to know where to focus.
Optional but valuable: If the following files exist, read them before starting passes 5 and 4 respectively. They provide the behavioral spec to compare code against:
findings/contracts/behavioral-contracts.md— enables spec-grounded analysis in passes 4 and 5.findings/protocols/protocols-and-state.md— enables state machine violation detection in pass 5.
If these files do not exist, the passes still work — they fall back to comparing code against its own documentation (docstrings, type signatures, comments, README).
Pass Execution Order
Run these passes sequentially. Read the pass file, scan the source, record findings, then move to the next pass.
| Pass | File | Focus |
|---|---|---|
| 1 | findings/defect-scan/passes/01-logic-and-correctness.md |
Dead code, boundary errors, null handling, boolean logic, control flow |
| 2 | findings/defect-scan/passes/02-error-handling.md |
Swallowed errors, missing cleanup, uncaught exceptions, retry gaps |
| 3 | findings/defect-scan/passes/03-concurrency-and-resources.md |
Race conditions, lock issues, async pitfalls, resource leaks |
| 4 | findings/defect-scan/passes/04-security-and-trust.md |
Input validation, auth gaps, secrets in code, trust boundaries |
| 5 | findings/defect-scan/passes/05-api-contract-violations.md |
Spec vs. implementation drift, return type mismatches, state machine violations |
| 6 | findings/defect-scan/passes/06-config-and-environment.md |
Hardcoded values, missing validation, dangerous defaults, OS assumptions |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +10 lines d65d6a154496
- 1mo ago Changed · +14 lines 971343bde03c
- 1mo ago First seen · 88 lines · 62 tokens per session scan A 932483cbb97d
scan-for-defects is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (6 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 1,920 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
code-review
Reviews code for bugs, security issues, and best practices.
resolve-review-pr
Review an existing fix PR using the audited repro and full diff, preserving branch and approval rules.
deep-analysis
Performs focused, depth-first investigation of specific reverse engineering questions through iterative analysis and database improvement. Answers questions like "What does this function do?", "Does this use crypto?", "What's the C2 address?", "Fix types in this function". Makes incremental improvements (renaming…
pyghidra-scripting
Write and run Python (PyGhidra) code inside the Ghidra session that ReVa's MCP server is already attached to, using the five ReVa scripting tools — run-script, list-scripts, read-script, write-script, edit-script. Use this whenever the user asks to execute Python against the current program, reach for the Ghidra Flat…
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
ctf-rev
Solve CTF reverse engineering challenges using systematic analysis to find flags, keys, or passwords. Use for crackmes, binary bombs, key validators, obfuscated code, algorithm recovery, or any challenge requiring program comprehension to extract hidden information.