A status report for a running team of coding agents working on an epic or batch of tickets. It shows overall progress, each ticket’s state, each agent’s current work, and notable events.

Use it to check an active epic run, review ticket progress, see what agents are doing, and identify notable problems or changes.

It gives a consistent view of a multi-agent run without requiring you to inspect each task separately.

team-status — Skill for Claude Code by phobologic/claude_code

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.

Any agent

npx skills add phobologic/claude_code_helpers --skill team-status

Clone the repo

git clone --depth 1 https://github.com/phobologic/claude_code_helpers

Made for: Claude Code.

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/phobologic/claude_code_helpers/team-status/github.svg)](https://agentmods.dev/skills/phobologic/claude_code_helpers/team-status)

Your own site

<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/team-status"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/team-status/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/team-status"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/team-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00090	$0.01226
Opus 5.5	$0.00036	$0.00490
Sonnet 5.5	$0.00018	$0.00245
Haiku 4.5	$0.00009	$0.00123

Measured 12d ago against content hash 8cc7ce571071, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 12d 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-status/SKILL.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 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 $ARGUMENTS contains 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 runs are active, list them and ask the user which one.
If no run is active and no argument was given, fall back to the most recently-touched epic: tk query '.type == "epic" and .status == "in-progress"' sorted by updated_at desc. If exactly one matches, use it; otherwise list candidates and ask.

Record:

EPIC_ID — the epic or batch ID
BRANCH — integration branch (epic/<id> or fix/batch-*) if one exists
RUN — the run label: the stamp shared by this run's agent names and worktree paths (e.g. epic-dag-20260906-143022), if one is in flight

Phase 2 — Gather data

Run these in parallel:

tk show <EPIC_ID> — epic title and metadata
tk query '.parent == "<EPIC_ID>"' — every child ticket with status, assignee, notes
ListAgents — every agent this session has spawned; the rows whose names carry this run's stamp are its pool, and each row says whether that agent is busy or idle right now
git -C <repo-root> worktree list — active worktrees for this run
git -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 blocked or whose parent is FINDINGS_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

Read the full file on GitHub · 105 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.

12d ago Changed · +9 lines 8cc7ce571071
1mo ago First seen · 96 lines · 90 tokens per session scan A 260eceb22efb

Subscribe to this mod's changes

team-status is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 1,226 once invoked, about $0.0004 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-31.

Building agents Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens