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 bostonaholic/team --skill team-fixgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/team-fix)<a href="https://agentmods.dev/skills/bostonaholic/team/team-fix"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-fix/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/bostonaholic/team/team-fix"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-fix.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.00030 | $0.00429 |
| Opus 5.5 | $0.00012 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
team-fix 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 13d 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.
What it actually says
Team Fix — Bug Fix Pipeline
Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.
Invocation is guarded per human control rules: the pipeline fires only on stated pipeline intent — a plain "fix this bug" asks for an inline fix, not this pipeline.
Core contracts
- Run
WORKTREE → REPRODUCE → RED → GREEN → VERIFY → SHIPin order. - For a ticket, read tracking rules; move the ticket to in-progress before work and in-review only after its draft PR becomes ready.
- When behavior looks deliberate, trace its rationale before changing it (see Execution).
- After Worktree, run each step in its own fresh subagent per the Execution reference's
## Step dispatch; keep gates, aborts, and ticket moves inline.
Procedure references
Read each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.
Applied principles
Read and apply: bug fix rules and execution rules.
What ships with it
11 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.
- agents/openai.yaml 171 B
- playbooks/bug-fix.md 2.8 KB
- references/01-input.md 533 B
- references/02-when-to-use.md 422 B
- references/03-pipeline.md 190 B
- references/04-setup.md 1.4 KB
- references/05-worktree.md 2.4 KB
- references/06-execution.md 2.8 KB
- references/07-ship.md 1.6 KB
- references/08-aborting.md 351 B
- references/diagnosis.md 2.9 KB
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.
- 13d ago Changed · +1 lines 326d51414f7d
- 14d ago Changed dfb8768c0d8f
- 24d ago Changed · -3 lines 9e6c9d93b3cb
- 28d ago Changed · -19 tokens per session 4aa1cbc62089
- 1mo ago Changed b2e9424a434c
- 1mo ago Changed · +3 lines 73e441f3acde
- 1mo ago Changed · -182 lines · -76 tokens per session 486adf68ae7f
- 1mo ago First seen · 221 lines · 125 tokens per session scan A b5b5e934b233
team-fix is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed 12d ago), licensed MIT. It adds 30 tokens to every session and 429 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-09-03.
Other skills, from other repositories
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.