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 JinPLu/Teamwork --skill teamwork-debuggit clone --depth 1 https://github.com/JinPLu/TeamworkWrote 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/jinplu/teamwork/teamwork-debug)<a href="https://agentmods.dev/skills/jinplu/teamwork/teamwork-debug"><img src="https://agentmods.dev/badge/skills/jinplu/teamwork/teamwork-debug/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/jinplu/teamwork/teamwork-debug"><img src="https://agentmods.dev/badge/skills/jinplu/teamwork/teamwork-debug.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.00045 | $0.00390 |
| Opus 5.5 | $0.00018 | $0.00156 |
| Sonnet 5.5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
teamwork-debug 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.
What it actually says
Teamwork Debug
Diagnose from the observed failure, not from a preset ceremony.
Read references/runtime-diagnosis.md for the detailed evidence and document
semantics.
Method
- Reproduce or directly inspect the failure and bound the first bad behavior.
- Form only hypotheses supported by evidence. One hypothesis is enough when a direct observation isolates the cause.
- Run the smallest observation that distinguishes the live alternatives. For a runtime unknown, use structured logging first when it is that discriminator; keep non-runtime or already-isolated failures probe-minimal.
- Locate the first bad owned boundary and state the supported cause.
- If the user authorized a fix, make the smallest complete repair and verify the same failing path. Remove temporary instrumentation.
- If evidence reveals a different failure, split it explicitly instead of silently changing scope.
freeze observe, instrument, and fix permission in any diagnosis brief. Diagnosis must not silently expand repair authority.
Do not guess a fix or retain temporary diagnostics.
Persistence
When a listed checkpoint fires, write in the same response cycle. If separate stable identities each cross a checkpoint, write each to its own path.
Cross-chat memory lives in one Markdown document from references/debug.md
at docs/teamwork/debug/<slug>.md. Same identity means the same
failure signature; reuse that path and name the document you read. A different
subject gets a new path.
Checkpoints: a cause is confirmed; an authorized fix is verified on the same path; the case is blocked with a durable next discriminator; or evidence splits a new failure with its own identity.
What ships with it
3 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 · 44 lines · 45 tokens per session scan A fae442997934
teamwork-debug is a skill published in the GitHub repository JinPLu/Teamwork (12 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 390 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
chisle-audit
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in…