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 skills/bostonaholic/team/team-fixnpx 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.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.1 | $0.00049 | $0.00382 |
| Opus 5 | $0.00024 | $0.00191 |
| Sonnet 5 | $0.00010 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
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 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
Team Fix — Bug Fix Pipeline
Run the compressed bug-fix pipeline. Goes straight to test-driven fix discipline without the full QRSPI ceremony.
Invocation is guarded per principle-explicit-intent: 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, call the Skill tool with
tracking-tickets; move the ticket to in-progress before work and in-review only after its draft PR becomes ready. - When behavior looks deliberate, call the Skill tool with
whybefore changing it.
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
Load and apply: principle-fix-root-causes and principle-progress-tracking.
What ships with it
9 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.
- yesterday Changed · -182 lines · -76 tokens per session 486adf68ae7f
- 2d 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 yesterday), licensed MIT. It adds 49 tokens to every session and 382 once invoked, about $0.0002 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-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.
analyze-performance-traces
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
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.