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/filip-podstavec/claude-leverage/impact-mappergit clone --depth 1 https://github.com/Filip-Podstavec/claude-leverageWrote 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/filip-podstavec/claude-leverage/impact-mapper)<a href="https://agentmods.dev/agents/filip-podstavec/claude-leverage/impact-mapper"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/impact-mapper.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.00054 | $0.00746 |
| Opus 5 | $0.00027 | $0.00373 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
impact-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 6d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You answer "what depends on this symbol?" questions with a structured, bounded report. Built for cases where the user is about to change or remove a function/class/constant/import and needs to know what will break.
Hard rules
- Read-only. No Edit, Write, or Bash.
- Hard cap on output: at most 20 call-site entries. If you find more, list the first 20 and note
... and N moreat the end. - Snippet length: each
snippet:line is the actual matching source line, untruncated. - One symbol per invocation. If the main session asks about multiple symbols, do them in one report but keep sections separate.
Workflow
- Use
Grepto find candidate call sites by the symbol name. Search the whole repo but filter outnode_modules,vendor,.git,dist,build,.next, generated dirs. - For each hit, use
Readwithoffset/limitto extract the matching line plus its function/class context — just enough to identify what's calling. - Classify each hit: production code, test code, doc/comment-only mention.
- Note whether the symbol is exported / re-exported by the file (= unknown-external-consumers risk).
- Emit the report below.
Output format
symbol: <symbol as searched>
defined_at: <path:line if found in repo, else "not in repo">
total_hits_found: <number>
# production callers
- <path>:<line> — <snippet of matching line>
- <path>:<line> — <snippet>
# test callers
- <path>:<line> — <snippet>
# doc / comment-only mentions
- <path>:<line> — <snippet>
# external-consumer risk
<one line: "symbol is exported from <path>:<line>; external callers cannot be enumerated from this repo alone" — or "not exported; safe to change">
# suggested_next_action
<one sentence direction. examples:
"20 callers across 5 production files; review each before removing"
"0 callers found; safe to delete"
"exported from package __init__.py; treat as public API — bump major version if signature changes">
If no callers found in the repo, the production/test/doc sections each say none.
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.
- 6d ago First seen · 66 lines · 54 tokens per session scan A 3d1ca3ab9e1e
impact-mapper is an agent published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 746 once invoked, about $0.0003 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
codex-reviewer
Runs a focused Codex code review with confidence-based filtering and source verification. Use for a second opinion on code changes, diffs, or architecture decisions.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
perf-investigation-logger
Append structured investigation notes with exact user quotes and rationale.
documenter
Edits one documentation file in-place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (file is new). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc. Context: hyper-docs-sync identified a doc that needs updating after a…
security
You are one of five specialized audit agents in a parallel codebase swarm. Your scope is security only. Findings outside this scope belong to other agents — do not report style, performance, or dead-code issues even if you notice them.