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 miltonian/cartographer --skill analyzegit clone --depth 1 https://github.com/miltonian/cartographerWrote 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/miltonian/cartographer/analyze)<a href="https://agentmods.dev/skills/miltonian/cartographer/analyze"><img src="https://agentmods.dev/badge/skills/miltonian/cartographer/analyze.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.00044 | $0.00355 |
| Opus 5 | $0.00022 | $0.00178 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
analyze 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 7d 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.
What it actually says
Codebase Analysis
Verify tools: call cartographer_get_summary. If it fails, stop — MCP
tools are not connected.
Set the project root: cartographer_set_project.
If analyzing a specific concern (e.g., "analyze auth"), create a perspective
first with cartographer_create_perspective — it auto-switches, so entities
you write next join it. No separate cartographer_switch_perspective needed.
How to Analyze
Behaviors first. Identify the most important things this system does. Trace each behavior from entry point to completion. Record every entity encountered along the flow. Record the path as a behavior slice.
Boundaries emerge from behaviors. Cluster entities that participate in the same flows. Name by concern, not by directory.
Evidence is mandatory. Every cartographer_write_entity and
cartographer_write_relationship call must include source anchors
(filePath, lineStart, lineEnd, snippet). Set confidence: proven for
direct observations, lower for inferences. Include reasoning for
anything below proven.
Descriptions are for everyone. Name entities by what they do, not how they're implemented. Behavior flows read like stories. Technical detail belongs in evidence anchors, not descriptions.
After Analysis
Call cartographer_get_summary and report what was found. Open the map
with cartographer_open_map.
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.
- 7d ago First seen · 42 lines · 44 tokens per session scan A 4bc58de8432d
analyze is a skill published in the GitHub repository miltonian/cartographer (1 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 355 once invoked, about $0.0002 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
truecourse-fix
Fix TrueCourse violations that have suggested fixes.
truecourse-list
List TrueCourse violations found in this repository.
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.…
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.