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/FarzamMohammadi/dev-toolboxWrote 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/farzammohammadi/dev-toolbox/map-reviewer)<a href="https://agentmods.dev/agents/farzammohammadi/dev-toolbox/map-reviewer"><img src="https://agentmods.dev/badge/agents/farzammohammadi/dev-toolbox/map-reviewer/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/farzammohammadi/dev-toolbox/map-reviewer"><img src="https://agentmods.dev/badge/agents/farzammohammadi/dev-toolbox/map-reviewer.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.00042 | $0.01529 |
| Opus 5.5 | $0.00017 | $0.00612 |
| Sonnet 5.5 | $0.00008 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
map-reviewer 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 271 lines · 42 tokens per session scan A 61a8b3edf7d5
map-reviewer is an agent published in the GitHub repository FarzamMohammadi/dev-toolbox (1 stars, last pushed 19d ago), with no licence file. It adds 42 tokens to every session and 1,529 once invoked, about $0.0002 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-31.
Other agents, from other repositories
bootstrap
Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core planner selected at Phase 0 — the first real workspace this project gets, since init with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. Reads the…
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
spec-reviewer
Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.
runtime-architect
Use when building or updating runtime layouts under runtimes/, the MCP single-source-of-truth, or cross-vendor sync utilities under tools/. Owns the six copy-pasteable layouts at runtimes/.claude/, runtimes/.codex/, runtimes/.gemini/, runtimes/.kiro/, runtimes/.cursor/, and runtimes/.devin/, plus runtimes/mcp/…
skill-author
Use when designing or extending skills under skills/. Owns the folder-per-skill convention with SKILL.md, the portable SpecRoute contract (name + description) and vendor-native frontmatter, the skill-template/ canonical layout, and skills/examples/ folders. Ensures skills are interactive parameterized workflows with a…