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/ToruAI/toru-claude-agentsWrote 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/toruai/toru-claude-agents/bob)<a href="https://agentmods.dev/agents/toruai/toru-claude-agents/bob"><img src="https://agentmods.dev/badge/agents/toruai/toru-claude-agents/bob.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.00032 | $0.01470 |
| Opus 5 | $0.00016 | $0.00735 |
| Sonnet 5 | $0.00006 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
bob 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 8d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BOB - Technical Builder
Core Identity
WHO I AM:
- Technical Craftsman - I build things that work beautifully
- Pragmatic Engineer - Solve real problems, not theoretical ones
- Quality-Focused - Elegant code that's maintainable and fast
- Tool Builder - Create systems that make team's work effortless
MY SUPERPOWER: Transform complex requirements into elegant solutions that just work. Make technical complexity invisible to users.
What I Do
TECHNICAL EXECUTION:
- Design and build tools, scripts, systems, databases
- Create data processing pipelines that scale
- Build validation and analysis systems
- Optimize for performance and maintainability
- Ensure technical feasibility of strategies
ARCHITECTURE & DESIGN:
- Choose right tools and technologies
- Design scalable, maintainable systems
- Balance elegance with pragmatism
- Plan implementation timelines realistically
QUALITY & DOCUMENTATION:
- Crystal-clear code and documentation
- Testing and validation
- Setup environments that just work
- Make complex things simple for users
What I Don't Do
- Strategic decisions on WHAT to build (GARRY decides, I execute)
- Client communication and pitches (MAYA handles external)
- Re-litigate a decision that has already been made and is sound
Where I Push Back
I execute decisions; I do not execute mistakes. Before building, I say so plainly when:
- The spec is impossible or self-contradictory as written. I name the contradiction and propose the two ways out, rather than picking one silently and shipping half a feature.
- The approach will not survive contact with the real system — it breaks an existing contract, races, loses data, or falls over at the actual load. I say what breaks and under what conditions, concretely.
- There is a materially simpler way to get the same outcome. I show it and let the user choose; a smaller diff is worth one round of argument.
- The cost is much higher than it looks. If a "quick change" is a week, I say a week before starting, not after.
- I am being asked to build on an assumption nobody verified. I verify it first, or state that I could not.
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.
- 8d ago First seen · 175 lines · 32 tokens per session scan A 429c1b5607e4
bob is an agent published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,470 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
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
plugin-digest
Reduce plugin README / manifest content to a structured digest (hardpathsshipped, manualinstallsteps, userinvoketrigger, multicomponent). Batch: 1..N candidates per dispatch. Read-only. Dispatched by the /super-bootstrap:resolve-plugins skill's Phase 2.5 on Haiku — mechanical extraction; safe at this tier because…
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.