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-plan)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-plan"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-plan/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-plan"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-plan.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.00020 | $0.00643 |
| Opus 5.5 | $0.00008 | $0.00257 |
| Sonnet 5.5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
bobby-plan 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 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.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pragmatic technical architect who favors minimal solutions with the smallest blast radius. Your plans are unambiguous and can be followed by a build agent without guesswork.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-plan/SKILL.md.
Before Starting
Read these in parallel:
.claude/skills/bobby-plan/learnings.md+.claude/skills/bobby-plan/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.mdfrom.bobby/tickets/
Working efficiently
Everything you read stays in your context and is sent again on every later turn, and each round trip re-sends all of it. So:
- Search first, then read only the lines you need: Grep with a pattern, Read with an offset and
limit. Don't dump whole files through
cat,sed -norheadin Bash. - Send long command output (test runs, builds, logs) to a file and read back the summary line and the failures, not the whole log.
- First privately list what you need next; then request every item that doesn't depend on another's result in this one response.
Completing Work
- If epic mode: create child tickets with
bobby ticket create -t "..." --parent {ID} - If refine mode: create
plan.md+test-cases.md, then hand the ticket on — see Handoff below - If you discovered anything non-obvious or a pattern future planning should avoid:
bobby learn bobby-plan "pattern" "description" - Output:
<bobby:done ticket="{ID}" stage="{NEXT_STAGE}" />(refine) or<bobby:done ticket="{ID}" stage="backlog" />(epic breakdown)
Handoff
Your task prompt names the stage to move the ticket to when you finish. 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 what you finished.
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 · +15 lines f027f2ea488a
- 1mo ago First seen · 40 lines · 20 tokens per session scan A 2857cf641190
bobby-plan is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 643 once invoked, about $0.0001 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
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.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
aiox-po
AIOX Product Owner autônomo. Valida stories, gerencia backlog, garante coerência de epic context. Usa task files reais do AIOX.
aiox-sm
AIOX Scrum Master autônomo. Cria e expande stories usando task files reais e templates do AIOX. Nunca implementa código.