A fast workflow for diagnosing and fixing an urgent production bug, meaning a problem affecting the live application.

Use it to create a hotfix branch, investigate the cause, repair application or data problems, run focused tests, deploy, update affected documentation, and merge the release.

It organizes emergency work around a minimal fix and focused testing, without a separate review stage, so the issue can move quickly toward deployment.

team-fix — Skill for Claude Code and Codex by bryanweaver: A fast workflow for diagnosing and fixing an urgent…

Install

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.

agentmods

npx agentmods add skills/bryanweaver/claude-agent-kit/team-fix

Any agent

npx skills add bryanweaver/claude-agent-kit --skill team-fix

Clone the repo

git clone --depth 1 https://github.com/bryanweaver/claude-agent-kit

Made for: Claude Code, Codex.

Or install team, the plugin that ships this one along with the rest of its 17 skills, 7 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-fix.svg)](https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-fix)

Your own site

<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-fix"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-fix.svg" alt="Measured on agentmods" height="20"></a>

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 708 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00014	$0.00708
Opus 5	$0.00007	$0.00354
Sonnet 5	$0.00003	$0.00142
Haiku 4.5	$0.00001	$0.00071

Measured 4d ago against content hash ba335747888f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

skills/team-fix/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix — Emergency Bug Fixes

Rapidly diagnose and fix production issues. Speed is the priority — no reviewer step.

Issue to fix: $ARGUMENTS

Execution

With Agent Teams (recommended)

Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Create a team and spawn teammates:

Create team named fix-<issue-slug>
Spawn teammates: shipper, full-stack-developer, database-admin (if data issue), documentor

Create the following task list with dependencies:

#	Task	Owner	Blocked By
1	Create hotfix branch `hotfix/<issue-id>` from main	shipper	—
2	Diagnose root cause and implement minimal fix	full-stack-developer	1
3	Fix data layer issues (if applicable)	database-admin	1
4	Commit fix with message `fix: <description>`	shipper	2, 3
5	Run focused tests and deploy	shipper	4
6	Update documentation if fix affects docs	documentor	5
7	Merge hotfix to main, tag patch release	shipper	5, 6

Parallelism: Tasks 2 and 3 can run simultaneously if both are needed.

Without Agent Teams (fallback)

Execute sequentially using the Task tool:

Task(shipper, "Create hotfix branch hotfix/<issue-id> from main")
Task(full-stack-developer, "Diagnose and fix: $ARGUMENTS")
Task(database-admin, "Fix data issues for: $ARGUMENTS") — only if data-related
Task(shipper, "Commit fix: fix: <description>")
Task(shipper, "Run focused tests on fix, deploy to production")
Task(documentor, "Update docs if fix affects documented behavior: $ARGUMENTS")
Task(shipper, "Merge hotfix to main, tag patch release")

Workflow Diagram

┌─────────┐     ┌──────────────────┐     ┌─────────┐     ┌──────────┐     ┌────────────┐     ┌─────────┐
│ Shipper │────►│ Full Stack Dev   │────►│ Shipper │────►│ Shipper  │────►│ Documentor │────►│ Shipper │
│ Hotfix  │     │ + DB Admin (||)  │     │ Commit  │     │Quick Test│     │ Update Docs│     │PR/Merge │
│ Branch  │     │ Diagnose & Fix   │     │   Fix   │     │ & Deploy │     └────────────┘     └─────────┘
└─────────┘     └──────────────────┘     └─────────┘     └──────────┘

Read the full file on GitHub · 61 lines

Changes

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 · 61 lines · 14 tokens per session scan A ba335747888f

Subscribe to this mod's changes

team-fix is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 708 once invoked, about $0.0001 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.

Debugging

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens