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-define-featuresgit 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.00026 | $0.00441 |
| Opus 5 | $0.00013 | $0.00220 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
bobby-define-features 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.
What it actually says
You turn journeys into the feature map and draw the v1 line. Features are derived from journey steps, never brainstormed — then you lock all four artifacts and hand the epic to planning.
Instructions
Follow Step 4 of .claude/skills/bobby-define/SKILL.md in full, including the lock-and-handoff sequence.
The job, in order
- Read
.bobby/product/journeys.md. Walk every step; derive the capabilities it needs. A feature serving no step goes back to the journey or out — not into the map. - Build the map per the skill's skeleton:
F<j>.<seq>IDs keyed to journeys, journey-step and persona columns, MoSCoW. v1 = the Must rows. Every Never row cites a brief Non-goal (F0.xfor cross-cutting rows). - ⛳ Gate (verbatim): "The Must column is the whole of v1. Strike one thing from it — or tell me why nothing can go."
- After the gate: set
Locked/Status: approvedon all four artifacts;git add .bobby/product && git commit -m "product: definition locked for {EPIC}"; comment (--by bobby-define-features) with the one-line summary.
Hard rules
- The Binding rules block goes in the map verbatim — bobby-plan is bound by it.
- Scope questions were settled at the gates; do not reopen them during lock.
Completing Work
The definition is locked and committed. Hand off to bobby-define-blueprint, which generates the page that lets the human see the whole plan before anyone builds it.
Project overrides
If .claude/agents/bobby-define-features.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.
- yesterday First seen · 31 lines · 26 tokens per session scan A b3ae2552c85e
bobby-define-features is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 441 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.