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/phobologic/claude_code_helpers/team-statusnpx skills add phobologic/claude_code_helpers --skill team-statusgit clone --depth 1 https://github.com/phobologic/claude_code_helpersWhat 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.00090 | $0.01085 |
| Opus 5 | $0.00045 | $0.00543 |
| Sonnet 5 | $0.00018 | $0.00217 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
team-status 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Status
Produce a single, consistently-shaped status report for the currently-running
agent team (/run-epic, /run-epic-dag, /fix-tickets, or /fix-tickets-dag).
The output of this skill should look the same every time it's invoked, so the user can scan it at a glance across runs. Do not editorialize or restructure the report; fill in the template below.
Phase 1 — Identify the run
Determine which run to report on:
- If
$ARGUMENTScontains an epic ID, use it. - Otherwise, look at the active team in this conversation:
- The team lead skill (e.g.
/run-epic-dag) holds the epic ID and ticket state in conversation context. Pull it from there. - If multiple teams are active, list them and ask the user which one.
- The team lead skill (e.g.
- If no team is active and no argument was given, fall back to the most
recently-touched epic:
tk query '.type == "epic" and .status == "in-progress"'sorted byupdated_atdesc. If exactly one matches, use it; otherwise list candidates and ask.
Record:
EPIC_ID— the epic or batch IDBRANCH— integration branch (epic/<id>orfix/batch-*) if one existsTEAM— the activeTeamCreateteam name, if any
Phase 2 — Gather data
Run these in parallel:
tk show <EPIC_ID>— epic title and metadatatk query '.parent == "<EPIC_ID>"'— every child ticket with status, assignee, notesTaskList— current agent tasks (if a team is active)git -C <repo-root> worktree list— active worktrees for this rungit -C <repo-root> log main..<BRANCH> --oneline— commits landed so far (if branch exists)
For "interesting events," scan:
- Notes on each child ticket (
tk show-multi) for the most recent 1-2 notes - Any tickets whose status flipped to
blockedor whose parent isFINDINGS_PARENT(out-of-scope findings created mid-run) - Quality-review rework loops (tickets with multiple in-progress→review cycles visible in their notes)
- Failed AC verifications still pending rework
- Agents in the pool that are idle while tickets remain unblocked
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 · 96 lines · 90 tokens per session scan A 260eceb22efb
team-status is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,085 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.