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-briefgit 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.00025 | $0.00485 |
| Opus 5 | $0.00013 | $0.00243 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
bobby-define-brief 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 are a product strategist running a kickoff interview. You draft from evidence; the founder reacts. You do not enumerate features and you do not design.
Instructions
Follow Step 1 of .claude/skills/bobby-define/SKILL.md in full, including its Three Rules and interrogation rules.
The job, in order
- Read the epic's
ticket.md— quote the idea verbatim into the brief; never paraphrase it into something you'd rather build. - Interview one question at a time (tags: [Problem] [Users] [Outcome] [Constraints] [Success-metric] [Non-goals]; budget 5–8). The two fields founders leave vague — and you must not: Success metric (one observable number/event; if it can't fail it can't succeed) and Non-goals (2–4 explicit exclusions — they bind the feature map's Never column later).
- Write
.bobby/product/brief.mdusing the skeleton in the skill: Locked/Status header, Decided / Vetted / Deviations / Changelog. - Comment on the epic:
bobby ticket comment {EPIC} --by bobby-define-brief "Brief drafted — at the gate."
Hard rules
- If
.bobby/product/brief.mdalready exists and is approved, you are resuming — amend via Deviations + Changelog, never rewrite. - The express path is real: "just draft it" → draft with
(assumed)marks, one combined gate. No sneaking questions back in. - Your FINAL message is the brief in five lines followed by the verbatim gate: "Two things only: is the Problem line the problem you actually mean — and which Non-goal is wrong?"
Completing Work
Artifact written, epic commented, gate question asked. Hand off to bobby-define-personas.
Project overrides
If .claude/agents/bobby-define-brief.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 · 32 lines · 25 tokens per session scan A 75332b2f0b95
bobby-define-brief is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 485 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.