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 commands/rube-de/cc-skills/bugfixgit clone --depth 1 https://github.com/rube-de/cc-skillsWrote 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/commands/rube-de/cc-skills/bugfix)<a href="https://agentmods.dev/commands/rube-de/cc-skills/bugfix"><img src="https://agentmods.dev/badge/commands/rube-de/cc-skills/bugfix.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.00821 |
| Opus 5 | $0.00028 | $0.00411 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
bugfix 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: Coordinator only. You MUST NOT use Edit, Write, or NotebookEdit tools on source code, test files, or project docs. All implementation, testing, review, and documentation MUST be delegated to teammates via SendMessage. If you find yourself about to edit a file, STOP and delegate to the appropriate teammate instead. You verify artifacts and manage git operations only.
/bugfix — TDD Bugfix Workflow
Target: $ARGUMENTS
Single-phase workflow: assemble bug spec, then run a red-green-refactor cycle with a Developer/Tester/Reviewer triad. No planning phase — the bug issue IS the plan.
bugfix-team
┌───────────────────────────────┐
│ Lead (You) │
│ ├── tester [tm] RED │
│ ├── developer [tm] GREEN │
│ ├── reviewer [tm] REVIEW │
│ └── researcher [sa] on-demand│
└───────────────────────────────┘
Flow: Tester → Developer → Tester → Developer → Tester → Reviewer
(RED) (GREEN) (VERIFY) (REFACTOR) (VERIFY) (REVIEW)
[tm] = teammate (Agent Team) [sa] = subagent
The bugfix-team label above is a role name; the actual team name created by the workflow is scoped per run as bugfix-<branch-slug>-<YYYYMMDD-HHMMSS>-<nonce> to avoid collisions on the global ~/.claude/teams/ namespace, where branch-slug is the current branch name with / replaced by -.
Step 0: Workflow Declaration
Print to the user before proceeding:
Workflow: bugfix
Roles: tester [tm], developer [tm], reviewer [tm], researcher [sa]
Pipeline: RED → GREEN → REFACTOR → REVIEW
Coordinator role: orchestration only — no direct file edits
PR: auto (pass --no-pr to commit only)
Execution
Follow the bugfix workflow defined in @bugfix-workflow.md.
Completion Audit
Before wrap-up, log which roles were actually used:
Bugfix complete:
- tester [tm]: [used / NOT USED]
- developer [tm]: [used / NOT USED]
- reviewer [tm]: [used / NOT USED]
- researcher [sa]: [used / NOT USED]
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.
- 4d ago First seen · 78 lines · 55 tokens per session scan A 2728581f5e87
bugfix is a command published in the GitHub repository rube-de/cc-skills (10 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 821 once invoked, about $0.0003 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 commands, from other repositories
init
Initialize agent-harness model routing for your Claude tier (subscription or API).
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
pb-week
Show this week's training plan as a visual, print-ready weekly card.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
design-review
Compare design (Figma URL or mockup image) against implementation to detect UI mismatches (colors, layout, typography).