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-scan-mechanicalgit 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-mechanical)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/defect-scan-mechanical"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/defect-scan-mechanical/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-mechanical"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/defect-scan-mechanical.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.00088 | $0.01082 |
| Opus 5.5 | $0.00035 | $0.00433 |
| Sonnet 5.5 | $0.00018 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
scan-for-defects-mechanical 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan For Defects — Mechanical Pass
This phase runs the early, mechanical half of the defect-scan methodology. It catches the bugs that are visible from local code reading without needing the contracts or protocols phases to be done first. The deeper passes (concurrency, security, API contract violations) live in the later defect-scan-semantic phase.
The source code to analyze is in the parent directory (../ relative to .codecarto/).
Prerequisites
Required:
findings/architecture/architecture-map.md— for the layer map and public surfaces.- The repository's own build and packaging surface, which pass 6 is about and which the source
files never mention: the package manifest (
package.json,pyproject.toml,go.mod,Cargo.toml, …) with itsfiles/include list, the compiler or bundler config (tsconfig.jsonand kin), the CI and release workflows (.github/workflows/*), and the ignore files. Three of the high findings in one self-audit came from these files alone; a scan that reads only source cannot see what ships or what runs in CI.
You do not need contracts or protocols for this phase. If those exist already, skim them as bonus context, but do not block on them — the mechanical pass is by design context-light.
Pass Execution Order
Run these three passes sequentially. Read the pass file, scan the source, record findings, then move to the next pass. Each pass file is the same one used by the legacy defect-scan phase — only the subset is different.
| 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 |
| 6 | findings/defect-scan/passes/06-config-and-environment.md |
Hardcoded values, missing validation, dangerous defaults, OS assumptions |
Passes 3, 4, and 5 are deferred to defect-scan-semantic because they benefit from contracts/protocols context.
What ships with it
1 file 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 · +6 lines 9a37dfe9306b
- 1mo ago Changed · +1 lines 610fbe4bf54d
- 1mo ago First seen · 61 lines · 88 tokens per session scan A 575ecd5727ae
scan-for-defects-mechanical is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (7 stars, last pushed 4d ago), licensed MIT. It adds 88 tokens to every session and 1,082 once invoked, about $0.0004 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.
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.
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…
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.
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…