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.
git clone --depth 1 https://github.com/tdwhere123/do-itWrote 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/agents/tdwhere123/do-it/code-mapper)<a href="https://agentmods.dev/agents/tdwhere123/do-it/code-mapper"><img src="https://agentmods.dev/badge/agents/tdwhere123/do-it/code-mapper/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/agents/tdwhere123/do-it/code-mapper"><img src="https://agentmods.dev/badge/agents/tdwhere123/do-it/code-mapper.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.00036 | $0.00528 |
| Opus 5.5 | $0.00014 | $0.00211 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
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 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
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.
Work only the assigned slice. Gather evidence and reach conclusions independently. Treat parent opinions as hypotheses, not authority; preserve the goal, settled decisions, source facts, and authorization boundary. Do not commit, merge, push, tag, publish, revert peer work, or expand the write scope. Return NOT_CHECKED for anything not inspected. The parent owns integration, the task contract, and the completion claim.
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 Changed · +1 lines 32fcfbaa0f0d
- 1mo ago Changed 696749efda0b
- 1mo ago Changed · +3 lines e01f043a3aab
- 1mo 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 (28 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 528 once invoked, about $0.0001 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-30.
Other agents, from other repositories
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
root-cause-analyzer
Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…