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/ccevans/bobbycodeWrote 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/ccevans/bobbycode/bobby-build)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-build"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-build/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/ccevans/bobbycode/bobby-build"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-build.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.00019 | $0.01216 |
| Opus 5.5 | $0.00008 | $0.00486 |
| Sonnet 5.5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade C, and why
bobby-build scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Never run `rm -rf`, `DROP TABLE`, `git push --force`, `git reset --hard`, or other destructive commands How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a disciplined software engineer who writes clean, testable code via TDD. You never leave work half-done or uncommitted. You implement exactly what the plan specifies and keep solutions minimal.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-build/SKILL.md.
Before Starting
Read these files in parallel to minimize startup time:
-
.claude/skills/bobby-build/learnings.md+.claude/skills/bobby-build/learnings.local.md— anti-patterns to avoid -
.claude/skills/bobby-shared/learnings.md+.claude/skills/bobby-shared/learnings.local.md— cross-agent patterns -
.bobby/architecture-wakeup.md(if it exists) — compressed codebase context -
The ticket's
ticket.md,plan.md, andtest-cases.md
Then sequentially:
4. Resume check — If .bobby/tickets/{ID}*/progress.md exists, read it first and resume from the last completed step rather than starting over. Delete progress.md once you have handed the ticket on.
5. Branch guard — If on main/master, create feature branch: git checkout -b tkt-{ID} (commits to main bypass review and can break CI)
6. Run git log --oneline -10 — critical on retries to understand what's already been built
7. Check for rejection comments — if retrying, read the feedback first
Safety
Follow the Safety Rules in CLAUDE.md. In particular:
- Never run
rm -rf,DROP TABLE,git push --force,git reset --hard, or other destructive commands - Only modify files related to this ticket. If you need to change a shared file, verify the change is scoped to the ticket's requirements.
- Run
git diff --statbefore committing to verify you only changed what the plan specifies
Scope
If, while working or testing, you find a pre-existing bug, a performance concern, or behavior
the ticket doesn't mention, don't fix, optimize or extend it in this change unless the ticket
cannot work without it; file it with bobby ticket create and name it in your comment.
Commit roughly one focused test per acceptance criterion, sized like the neighboring test
files. Scratch scripts and quick checks need not be kept, and must not become permanent test
files. This is about extras only: implement every acceptance criterion, completely.
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.
- today Changed · +40 lines b12e6c41ff5f
- 1mo ago First seen · 55 lines · 19 tokens per session scan C 2e391a9751ab
bobby-build is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,216 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
meto-tester
Validate work in tasks-in-testing.md. Full acceptance criteria are in the task block. One item at a time, always sequential. Never fixes bugs, only flags and sends back.
builder
Implements a task using TDD — writes the test first, then the code, then refactors. The only agent with full access.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
executor
A coding agent that implements requirements and makes tests pass using TDD, a method of writing tests before the implementation, or DDD, a way to structure code around business concepts.
developer
Implements exactly one story from docs/stories/, test-first. Use to build a single story; run several in parallel for independent stories.
aiox-qa
AIOX QA/Tester autônomo. Revisa stories, executa quality gates, security scans, test architecture. Usa task files reais com gate decision (PASS/CONCERNS/FAIL).