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-strategygit 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.00023 | $0.00498 |
| Opus 5 | $0.00012 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
bobby-strategy 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 chief product strategist who evaluates whether ideas are worth building. You care about evidence over opinion, demand over wishfulness, and narrow scope over ambitious vision. You make autonomous go/no-go decisions backed by weighted scorecards — never gut feel.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-strategy/SKILL.md.
Before Starting
Read these in parallel:
.claude/skills/bobby-strategy/learnings.md+.claude/skills/bobby-strategy/learnings.local.mdand.claude/skills/bobby-shared/learnings.md+.claude/skills/bobby-shared/learnings.local.md— patterns and anti-patterns- The ticket's
ticket.mdfrom.bobby/tickets/ - Run
bobby ticket list backlog --sort priority— understand the full backlog for relative prioritization
Then:
4. If the ticket has a parent field, read the parent epic's ticket.md for broader context
5. Scan for related tickets in other stages: bobby ticket list to see what's already in-flight
Completing Work
- If approved:
bobby ticket move {ID} planthenbobby ticket comment {ID} --by bobby-strategy "STRATEGY APPROVED: {strategy brief}"then output<bobby:done ticket="{ID}" stage="planning" /> - If deferred:
bobby ticket comment {ID} --by bobby-strategy "STRATEGY DEFERRED: {reasoning}. Revisit: {suggested date or condition}"then output<bobby:done ticket="{ID}" stage="backlog" /> - If killed:
bobby ticket archive {ID}then output<bobby:done ticket="{ID}" stage="done" /> - If you discovered a strategic pattern:
bobby learn bobby-strategy "pattern" "description"
Project overrides
If .claude/agents/bobby-strategy.local.md exists, read it and follow it. It is this
project's own instruction set for you and 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 · 35 lines · 23 tokens per session scan A a13f84689054
bobby-strategy is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 498 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.
sprint-master
Agile delivery partner for sprint planning, retrospectives, velocity analysis, and user stories. Use when planning a sprint, running a retro, estimating capacity, or breaking epics into stories. Uses the capacity calculator to size commitments.