team-status

team-status is a command for coding agents from wshobson/agents. It costs 14 tokens per session (448 once invoked), scanned A, original, MIT.

A command for showing the members and tasks of an active group of coding agents. It can display who is working, which tasks are assigned, and what remains to be done.

In plain words
What is it for?
Use it to inspect a team’s members, task details, or both, with optional filtering and JSON output.
Why use it?
It gives a single view of team activity and task progress when work is split among several agents.

Command

Part of the agent-teams plugin — 6 skills, 7 commands, 4 agents shipped together

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 commands/wshobson/agents/team-status
Clone the repo
git clone --depth 1 https://github.com/wshobson/agents

Or install agent-teams, the plugin that ships this one along with the rest of its 6 skills, 7 commands, 4 agents.

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.

agentmods badge for team-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/wshobson/agents/team-status.svg)](https://agentmods.dev/commands/wshobson/agents/team-status)
Your own site
<a href="https://agentmods.dev/commands/wshobson/agents/team-status"><img src="https://agentmods.dev/badge/commands/wshobson/agents/team-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 448 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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00448
Opus 5 $0.00007 $0.00224
Sonnet 5 $0.00003 $0.00090
Haiku 4.5 $0.00001 $0.00045

Measured 4d ago against content hash ac797ec168d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

plugins/agent-teams/commands/team-status.md · 61 lines

What it actually says

Team Status

Display the current state of an active agent team including members, tasks, and progress.

Phase 1: Team Discovery

  1. Parse $ARGUMENTS for team name and flags:

    • If team name provided, use it directly
    • If no team name, check ~/.claude/teams/ for active teams
    • If multiple teams exist and no name specified, list all teams and ask user to choose
    • --tasks: show only task details
    • --members: show only member details
    • --json: output raw JSON instead of formatted table
  2. Read team config from ~/.claude/teams/{team-name}/config.json using the Read tool

  3. Call TaskList to get current task state

Phase 2: Status Display

Members Table

Display each team member with their current state:

Team: {team-name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Members:
  Name              Role              Status
  ─────────────────────────────────────────
  security-rev      team-reviewer     working on task #2
  perf-rev          team-reviewer     idle
  arch-rev          team-reviewer     working on task #4

Tasks Table

Display tasks with status, assignee, and dependencies:

Tasks:
  ID   Status        Owner           Subject
  ─────────────────────────────────────────────────
  #1   completed     security-rev    Review auth module
  #2   in_progress   security-rev    Review API endpoints
  #3   completed     perf-rev        Profile database queries
  #4   in_progress   arch-rev        Analyze module structure
  #5   pending       (unassigned)    Consolidate findings

Progress: 40% (2/5 completed)

JSON Output

If --json flag is set, output the raw team config and task list as JSON.

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.

  1. 4d ago First seen · 61 lines · 14 tokens per session scan A ac797ec168d3

Subscribe to this mod's changes

team-status is a command published in the GitHub repository wshobson/agents (39,386 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 448 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-30.