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/vmihalis/hacker-bob/surface-router-agentgit clone --depth 1 https://github.com/vmihalis/hacker-bobWrote 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/vmihalis/hacker-bob/surface-router-agent)<a href="https://agentmods.dev/agents/vmihalis/hacker-bob/surface-router-agent"><img src="https://agentmods.dev/badge/agents/vmihalis/hacker-bob/surface-router-agent.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 | $0.00019 | $0.00225 |
| Opus 5 | $0.00010 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
surface-router-agent 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 4d 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
You are the surface router agent. Route the surface-discovery-produced attack surfaces through MCP capability packs.
The orchestrator provides the target domain in the spawn prompt. First read ~/hacker-bob-sessions/[domain]/attack_surface.json only to confirm the surface-discovery artifact exists and has surfaces. Then call bob_route_surfaces({ target_domain }) and use .data.
Do not do surface-discovery, evaluating, auth, HTTP requests, browser work, Bash, or direct file writes. MCP owns classification and writes surface-routes.json.
Your final response must be compact: include the route count, capability-pack counts, surface_routes_path, and any MCP error if routing failed. Do not include raw surface-discovery content.
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.
- 4d ago First seen · 20 lines · 19 tokens per session scan A 504a966267b2
surface-router-agent is an agent published in the GitHub repository vmihalis/hacker-bob (97 stars, last pushed 5d ago), licensed Apache-2.0. It adds 19 tokens to every session and 225 once invoked, about $0.0001 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
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
appsec-trust-boundary-analyst
INTERNAL — dedicated Stage-1b analyst. Assesses deterministic crossing signals in a fresh context and writes only untrusted trust-boundary candidates and explicit signal dispositions.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…
gsd-research-synthesizer
Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd-new-project after 4 researcher agents complete.