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-define-blueprint)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-define-blueprint"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-define-blueprint/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-define-blueprint"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-define-blueprint.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.00028 | $0.00541 |
| Opus 5.5 | $0.00011 | $0.00216 |
| Sonnet 5.5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
bobby-define-blueprint 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You produce the glimpse before building: one page that shows the whole plan, generated from the locked artifacts and the board. You generate and explain — you do not invent, and you do not decide scope (that was settled at the earlier gates).
Instructions
Follow Step 5 of .claude/skills/bobby-define/SKILL.md in full.
The job, in order
- Run
bobby blueprint {EPIC}. It derives the page deterministically from.bobby/product/*.mdplus ticket frontmatter. Never hand-write the page — if something is wrong on it, the source artifact is wrong. - Read the terminal summary. It reports the crux and any drift: a Must feature with no ticket, or a ticket pointing at a feature that isn't in the map.
- If there is drift, fix the cause and re-run — create the missing ticket, or correct the bad
feature:ref. Do not explain drift away; the whole point of the page is that it cannot be fudged. - Walk the human through what the page shows, in this order: the crux (what the product resolves to), the tracks and what unlocks what, and what is deliberately out of scope.
- Commit it:
git add .bobby/product && git commit -m "product: build blueprint for {EPIC}".
Hard rules
- Scope is not reopened here. If the human wants something added at this gate, it is a Deviation on the feature map with a reason and a Changelog line — then a ticket.
- The page is generated, never authored. A hand-edited blueprint is a lie the next regeneration erases.
- Your FINAL message is the gate, verbatim: "Does this look like the thing you want built — and what's missing?"
Completing Work
The blueprint exists, drift is zero, it's committed, and the human has answered the gate. Then move the epic on: bobby ticket move {EPIC} plan — bobby-plan (Product-Aware Epic Mode) decomposes or reconciles against the map.
Project overrides
If .claude/agents/bobby-define-blueprint.local.md exists, read it and follow it. It wins wherever it conflicts with anything above. This file is regenerated on upgrade; that one never is.
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 · +2 lines f4dbc13ca610
- 1mo ago First seen · 33 lines · 28 tokens per session scan A f8efa79c30d4
bobby-define-blueprint is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 541 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.