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 skills add ccevans/bobbycode --skill bobby-strategygit 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/skills/ccevans/bobbycode/bobby-strategy)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-strategy"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-strategy/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/skills/ccevans/bobbycode/bobby-strategy"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.02426 |
| Opus 5.5 | $0.00021 | $0.00970 |
| Sonnet 5.5 | $0.00011 | $0.00485 |
| Haiku 4.5 | $0.00005 | $0.00243 |
Grade A, and why
strategy-gate 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 1mo ago.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Strategy Skill
Pre-planning gate that validates whether a ticket is worth building. Evaluates demand evidence, status quo alternatives, scope optimization, and impact scoring. Makes autonomous approve/defer/kill decisions.
Before Starting
- Check learnings — Read
.claude/skills/bobby-strategy/learnings.md+.claude/skills/bobby-strategy/learnings.local.md - Read the ticket — title, description, acceptance criteria, priority, type, area
- Survey the backlog —
bobby ticket list backlog --sort priorityto understand relative positioning - Check in-flight work —
bobby ticket list planning,bobby ticket list buildingto see current capacity
Investigation First
<investigation_rules> Before forming any strategic opinion:
- Read the ticket's full description, not just the title
- Check for existing tickets that overlap or duplicate this one: scan the backlog and in-flight stages
- If the ticket references a user need, look for evidence (bug reports, comments, related tickets)
- If the ticket has a parent epic, read the epic's ticket.md and any existing plan.md
- Read the project's README.md or CLAUDE.md to understand the product's current state and priorities
- Do not evaluate implementation feasibility — that's bobby-plan's job
- Do not design solutions — evaluate the problem's worthiness </investigation_rules>
Evaluation Framework
Run these six assessments sequentially. Each builds on the prior.
1. Demand Validation
<demand_validation> Core question: Is there real evidence someone needs this?
Evaluate:
- Behavioral evidence: Bug reports, support requests, workaround usage, repeated asks in comments
- Specificity test: Can you name a specific user or scenario that needs this? "Users want" is vague; "Users who try to export CSVs with >1000 rows get a timeout" is specific
- Interest vs. demand: Hypothetical interest ("it would be nice") is NOT demand. Demand requires evidence of pain or blocked workflows
- Frequency: Is this a daily problem, weekly annoyance, or rare edge case?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 263 lines · 53 tokens per session scan A e53f1c846654
strategy-gate is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 2,426 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
full-sdc
EXECUTE lean Full Story Development Cycle for one story: plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/. Use when: full-sdc, full cycle, SDC, run story end-to-end.
wave-execute
EXECUTE a lean wave — plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops. Use when: wave-execute, run wave, epic wave, parallel stories SDC.
close-story
Finalize bookkeeping for a story already completed by QA. Never changes lifecycle status. Use when: close story, close-story, story Done, /close-story.
develop-story
Implement a story (Ready → InProgress → ready for review). Runs the OSS develop task. Use when: develop story, develop, /develop-story, implement ACs.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.