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-semanticgit 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-semantic)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/defect-scan-semantic"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/defect-scan-semantic.svg" alt="Measured on agentmods" 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.00087 | $0.01040 |
| Opus 5 | $0.00044 | $0.00520 |
| Sonnet 5 | $0.00017 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
scan-for-defects-semantic 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 today.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan For Defects — Semantic Pass
This phase runs the deep, semantic half of the defect-scan methodology. The findings here only become legible once you know what the code is supposed to do — that is what the contracts and protocols phases give you. The early mechanical bugs (passes 1, 2, 6) were caught in the earlier defect-scan-mechanical phase.
The source code to analyze is in the parent directory (../ relative to .codecarto/).
Prerequisites
Required:
findings/architecture/architecture-map.mdfindings/contracts/behavioral-contracts.md— pass 5 needs this to define "violation."findings/protocols/protocols-and-state.md— passes 3 and 5 need this for state machine and event-ordering analysis.findings/defect-scan-mechanical/mechanical-defects.md— read so you do not re-flag what the mechanical phase already covered.
If any prerequisite is missing, stop and surface the gap. The semantic pass is the paid-for benefit of running the mechanical phase early; do not regress it by running the semantic pass blind.
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 reused from the legacy defect-scan phase.
| Pass | File | Focus |
|---|---|---|
| 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 |
Prioritization
Use the contracts and protocols outputs to decide emphasis:
- No concurrency model in protocols? Skim pass 3, focus elsewhere.
- No auth system in contracts? Skip the auth sections of pass 4, still check input validation.
- Heavy state machine in protocols? Spend extra time on pass 5.
- Many features in contracts marked "core" or "important"? Pass 5 spec-vs-impl drift on those is high-value.
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.
- today Changed · +2 lines 724d5e8a762c
- 7d ago First seen · 55 lines · 87 tokens per session scan A f6509a00929d
scan-for-defects-semantic is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (4 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,040 once invoked, about $0.0004 per session on Opus 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
dx-audit
Audits libraries, CLIs, and SDKs using 38 rules for public contracts, package exports, piped output, errors, and configuration. Use when asked to "audit my CLI", "review my SDK", "make this agent-friendly", or diagnose package type resolution. For agentic product trust use ax-audit; for docs use docs-writing.
vibedrift-drift-check
Use when writing or changing code in an existing repository to keep new code consistent with the repo's own conventions and avoid duplicating code that already exists. Checks a proposed function against the repo's dominant patterns and existing functions BEFORE it lands, turning drift detection into drift prevention.…
perf
Performance optimizer for loops, DB queries, rendering, and batch operations. Catches N+1 queries, missing indexes, and unnecessary re-renders.
knip
Find dead code, unused files, unused exports, and unused dependencies in a JavaScript/TypeScript project using knip. Use before a refactor, before a PR, or when the user asks to clean up bloat, remove unused deps, or shrink the codebase.
proactive-analysis
Automatically run a tech-debt scan before opening a pull request, after large refactors, or when the user asks for a code review — surface actionable findings without being asked.
edge-case-hunter
Exhaustive edge-case review that traces branching paths and boundary conditions in a diff or code sample and reports only unhandled cases. Use when the user asks to hunt edge cases, boundary conditions, missing guards, or wants an edge-case-focused review.