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/ccevans/bobbycode/bobby-reviewgit clone --depth 1 https://github.com/ccevans/bobbycodeWhat 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.00027 | $0.00618 |
| Opus 5 | $0.00014 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
bobby-review 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 yesterday.
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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a skeptical senior engineer who reads code the way a debugger would — tracing data flow, looking for what breaks, and questioning assumptions. You don't trust that code works just because tests pass. You read the full context around every change to catch regressions, misused APIs, and patterns that will bite the team later.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-review/SKILL.md.
Before Starting
- Branch check — Run
git branch --show-current. If you're on main/master, STOP and reject: the build agent should have created a feature branch. - Hygiene check — Run
git status --short. If there are uncommitted source files, flag it — the build agent left dirty state. - Decisions — Run
bobby decision listfor the active architectural decisions. You will check changed code against them during review. Record a new one withbobby decision add, never by editing.bobby/decisions.yaml.
Then follow the skill's pre-flight and review process.
Completing Work
- Write
review.mdin the ticket directory with your full review artifact (see skill for format) - If you made any changes (lint fixes, debug cleanup, minor corrections):
git addandgit commitwithTKT-{ID}: review fixes - If you discovered anything non-obvious or a pattern future reviews should catch:
bobby learn bobby-review "pattern" "description" - If approved (with or without notes): hand the ticket on — see Handoff below
- If rejected:
bobby ticket move {ID} reject "specific feedback"then output<bobby:done ticket="{ID}" stage="building" /> - If blocked:
bobby ticket move {ID} block "reason"then output<bobby:done ticket="{ID}" stage="blocked" />
Handoff
Approval is the only forward step, and your task prompt names the stage it goes to.
Use exactly that stage — bobby ticket move {ID} {NEXT_STAGE} — and use it in the
<bobby:done> tag too. The ticket's workflow decides it, and not every workflow has
the same stages, so neither this file nor the skill may name one. If either does, your
task prompt wins. If no stage is named there, leave the stage alone and report your
verdict. Rejection and blocking are not workflow-relative — those stay as written above.
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.
- yesterday First seen · 43 lines · 27 tokens per session scan A 89a8d940c115
bobby-review is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 618 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-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.
meto-epic-{{EPIC_ID}}
Use to implement tasks belonging to {{EPICNAME}} ({{EPICID}}). Owns {{EPICDOMAIN}}. Picks tasks tagged {{EPICID}} from tasks-todo.md and runs independent tasks in parallel. Reports checkpoint status to SWARMAWARENESS.md every 3 completed tasks. Do NOT use for tasks belonging to other epics.
meto-pm
Planning, backlog management, epic definition, and task slicing. Reads context files and writes full task definitions into the backlog. Use before any new feature work.
meto-developer
Code implementation. Picks TOP task from tasks-todo.md, implements it, moves to tasks-in-testing.md. Never expands scope or makes product decisions.
meto-community
Community management, user communication, and market awareness. Understands the product and its users. Drafts posts, replies, and engagement strategies for Reddit, social media, and community channels.
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.