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-workflowgit 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-workflow)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-workflow"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-workflow/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-workflow"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-workflow.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.00081 | $0.01326 |
| Opus 5.5 | $0.00032 | $0.00530 |
| Sonnet 5.5 | $0.00016 | $0.00265 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
run-workflow 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Workflow Skill
Orchestrates the ticket lifecycle: planning → building → reviewing → testing. Auto-chains agents and retries on rejection. Stops at shipping — use
bobby run shipseparately to create PRs and merge.
Before Starting
-
Ticket selection — If ticket IDs were provided as arguments, use those. Otherwise, discover and present tickets: a) Run
bobby ticket list planningandbobby ticket list backlogto find tickets ready to start b) Runbobby ticket list building,bobby ticket list reviewing,bobby ticket list testingto find in-progress tickets that can be resumed c) Present the results to the user in two groups:Ready to start:
Ticket Title Stage ... ... backlog/planning Resumable (in progress):
Ticket Title Stage ... ... building/reviewing/testing d) Ask the user which tickets to workflow (specific IDs or "all") e) Wait for the user's response before proceeding. Do not auto-select.
-
Branch guard — Run
git branch --show-current. If on main/master, create a feature branch:git checkout -b tkt-{first-ticket-ID}. NEVER commit directly to main/master.
Safety Limits
- Max retries per ticket: 3 (when an agent rejects, loop back to building)
- Max total agent invocations: 20 (across all tickets — stop and report if hit)
Workflow Stages
| Stage | Agent | What it does |
|---|---|---|
| planning | bobby-plan | Creates plan.md + test-cases.md |
| building | bobby-build | Implements the plan, commits code |
| reviewing | bobby-review | Code review — runs tests, lint, checks ACs |
| testing | bobby-test | Live app verification — browser + API testing |
Note: Shipping is handled separately via
bobby run ship. The workflow stops once a ticket reaches the shipping stage.
Orchestration Process
For each ticket, sequentially:
1. Read Ticket State
Read .bobby/tickets/{ID}*/ticket.md frontmatter to determine the current stage.
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 · 113 lines · 81 tokens per session scan A 8930bbc0faae
run-workflow is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,326 once invoked, about $0.0003 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.