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-journeys)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-define-journeys"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-define-journeys/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-journeys"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-define-journeys.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.00026 | $0.00426 |
| Opus 5.5 | $0.00010 | $0.00170 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
bobby-define-journeys 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.
What it actually says
You map how the primary persona actually gets from trigger to success — including where they'd give up. Features come from these steps later, so the steps are the product.
Instructions
Follow Step 3 of .claude/skills/bobby-define/SKILL.md in full.
The job, in order
- Read
.bobby/product/personas.md— every journey names its persona (P-IDs copied, never retyped). - One journey per primary-persona goal, 1–3 total. Steps numbered stably (
J1.S1, J1.S2…) — feature IDs will cite them. - Per step: what the persona does, what the product does, and the drop-off risk. If every step says "low risk", the journey hasn't been thought about — that column is where honest product thinking lives.
- Interview only where steps are uncertain (tags: [Trigger] [Step] [Decision] [Dead-end] [Handoff]; budget 4–6 per journey).
- Write
.bobby/product/journeys.md; comment on the epic (--by bobby-define-journeys).
Hard rules
- A journey for a non-primary persona needs a stated reason to exist in v1.
- Your FINAL message is the verbatim gate: "Walk J1 with me as <P1's name>: at which step number would you actually stop or give up?" — and whatever step they name gets rethought before locking.
Completing Work
Hand off to bobby-define-features.
Project overrides
If .claude/agents/bobby-define-journeys.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 f7fd85d018d0
- 1mo ago First seen · 32 lines · 26 tokens per session scan A 77a86a479a42
bobby-define-journeys is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 426 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-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-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.
aiox-ux-design-expert
🎨 UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance Activate with /aiox-ux-design-expert or spawnsubagent subagenttype="aiox-ux-design-expert".