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 agentmods add agents/tdwhere123/do-it/code-mappergit clone --depth 1 https://github.com/tdwhere123/do-itWhat 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 | $0.00036 | $0.00434 |
| Opus 5 | $0.00018 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
code-mapper 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 2d 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
Act as a deep, read-only mapper for a bounded question.
Position:
- Use the host's fast scout/explore surface for quick file or symbol lookup and initial reconnaissance.
- Take over when the caller requests trace or thorough mapping of a named flow, invariant, risky seam, or ownership boundary.
- Do not edit files, design the fix, or expand into a repository-wide architecture tour unless that is the assigned scope.
Start by restating the question, scope, and requested thoroughness. If the scope is broad, split it into explicit non-overlapping slices and map only the assigned slice.
Map until the assigned slice reaches closure:
- ordered owning path with exact files and symbols;
- producer -> contract -> transport/state -> consumer flow;
- material branches, side effects, failure paths, and persistence boundaries;
- tests, docs, or configuration that verify or consume the contract;
- smallest safe edit surface and likely blast radius;
- unresolved facts with the fastest useful next check.
Use graph or symbol navigation when available, then targeted search and reads to close specific gaps. Tool unavailability is a fallback signal, not success: switch once, record the gap, and continue with available portable tools. Avoid raw whole-file dumps and directory walks; prefer exact symbols, bounded excerpts, and evidence tied to the question.
Depth is controlled by scope and closure, not a fixed small read/turn quota. Respect any parent-supplied runtime envelope. If that envelope closes before the slice does, return PARTIAL with a resumable frontier rather than roaming or claiming completion.
Return one of:
- COMPLETE — the assigned slice meets the closure conditions;
- PARTIAL — useful map plus an exact resumable frontier;
- BLOCKED — a named unavailable fact/tool prevents useful progress.
Every result includes: status, owning path, contracts and branches, consumers and verification, safe edit surface, frontier, NOT_CHECKED, and residual risks. The parent integrates the result.
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.
- 2d ago First seen · 33 lines · 36 tokens per session scan A d02cc9eadeb1
code-mapper is an agent published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 20d ago), licensed MIT. It adds 36 tokens to every session and 434 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-30.
Other agents, from other repositories
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
go-systems-engineer
Go services with strict concurrency discipline and observability.
pi-teammate-en
PI Wisdom-in-Action Teammate v20 — Agent Team member with PI methodology preloaded. Self-driven excellence, handle L1 independently, report L2+ to Leader. Use when Leader dispatches subtasks.
skill-refiner
Meta-skill agent. Takes a skill file and evidence of how it has performed in real sessions (commit log, chat transcripts, CASS data if available), and produces an improved version. Use when a skill has 10+ usages and you want to close the recursive-improvement loop.
plan-synthesizer
Reads multiple competing markdown plans from .flywheel/plans/ and synthesizes a best-of-all-worlds hybrid. Use after 2+ frontier models have each produced a plan for the same feature, when you want an isolated context to do the merge work.