LegendaryTeam_For_Claude: Command for Claude Code

.claude/commands/team-status.md

team-status is a command for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 0 tokens per session (741 once invoked), scanned B, original, MIT.

A command that shows the current status of parallel autonomous teams, including active, completed, and queued work.

In plain words
What is it for?
Use it to check team progress, assigned tasks, completion details, and reported efficiency information.
Why use it?
It gives you one view of what separate teams are doing and which tasks still need review.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything LegendaryTeam_For_Claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/team-status.md
Clone the repo
git clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_Claude

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.

agentmods badge for team-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/team-status/github.svg)](https://agentmods.dev/commands/regardv/legendaryteam_for_claude/team-status)
Your own site
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/team-status"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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.

agentmods 80×15 button for team-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/team-status"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/team-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 741 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00741
Opus 5 $0.00000 $0.00370
Sonnet 5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

Measured 11d ago against content hash f022f3a00a5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

team-status scanned grade B with 1 finding 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 11d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/cache/team-status.json
.claude/commands/team-status.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Status

Display the status of all active parallel autonomous teams.

What this command does

Shows real-time status of:

  • Active autonomous execution teams (currently working)
  • Completed teams (finished today)
  • Queued tasks waiting for review
  • Parallel efficiency metrics

Implementation

Read and display the team status from:

cat .claude/cache/team-status.json

Then format in a user-friendly dashboard format:

╔═══════════════════════════════════════════════════════════╗
║ PARALLEL AUTONOMOUS TEAMS STATUS                          ║
╠═══════════════════════════════════════════════════════════╣
║ 🟢 ACTIVE TEAMS (5)                                       ║
╚═══════════════════════════════════════════════════════════╝

Team 1: @DatabaseAgent
  Task: Create orders table
  Progress: ████████░░ 80%
  Started: 10 minutes ago
  ETA: 2 minutes
  Files: migrations/003_create_orders.sql

Team 2: @UIAgent
  Task: ProductCard component
  Progress: ██████████ 100% ✓
  Completed: 2 minutes ago
  Files: components/ProductCard.tsx, components/ProductCard.test.tsx

Team 3: @APIAgent
  Task: Order endpoints
  Progress: ██████░░░░ 60%
  Started: 15 minutes ago
  ETA: 10 minutes
  Files: routes/orders.ts

Team 4: @TestAgent
  Task: Integration tests for checkout
  Progress: ████░░░░░░ 40%
  Started: 8 minutes ago
  ETA: 12 minutes
  Files: tests/integration/checkout.test.ts

Team 5: @RefactorAgent
  Task: Extract error handler from UserController
  Progress: ███████░░░ 70%
  Started: 12 minutes ago
  ETA: 5 minutes
  Files: controllers/UserController.ts

═══════════════════════════════════════════════════════════

🟡 HUMAN REVIEW QUEUE (2)

[HIGH] OAuth integration        ⏱️  Waiting 12 min
[MED]  Microservices split      ⏱️  Waiting 8 min

═══════════════════════════════════════════════════════════

📊 TODAY'S METRICS

Completed: 12 tasks
Average wait time: 8 minutes
Parallel efficiency: 5.2x faster
Auto-proceed accuracy: 95% (19/20 succeeded)

═══════════════════════════════════════════════════════════

Commands:
  /review-queue   - Review queued tasks
  /team-status    - Refresh this view (this command)
  /approve-task   - Approve a queued task
  /reject-task    - Reject a queued task

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

  1. 11d ago First seen · 109 lines · 0 tokens per session scan B f022f3a00a5b

Subscribe to this mod's changes

team-status is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 741 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.