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/jinplu/teamwork/teamwork-debugnpx skills add JinPLu/Teamwork --skill teamwork-debuggit clone --depth 1 https://github.com/JinPLu/TeamworkWhat 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.00045 | $0.00390 |
| Opus 5 | $0.00023 | $0.00195 |
| Sonnet 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 2d 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.
- 2d ago First seen · 44 lines · 45 tokens per session scan A fae442997934
teamwork-debug is a skill published in the GitHub repository JinPLu/Teamwork (11 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 390 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-08-30.
Other skills, from other repositories
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.