devteam-status

A status command for a multi-agent development system. It reports system health, current progress, costs, execution history, and agent performance.

In plain words
What is it for?
It is for viewing the current session, recent runs, cost details, agent metrics, or a comprehensive status report.
Why use it?
It puts session and execution information in one report instead of requiring separate checks of logs and stored state.

Skill for Claude CodeCodex

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 skills/michael-harris/devteam/devteam-status
Any agent
npx skills add michael-harris/devteam --skill devteam-status
Clone the repo
git clone --depth 1 https://github.com/michael-harris/devteam

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,187 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.00017 $0.02187
Opus 5 $0.00009 $0.01094
Sonnet 5 $0.00003 $0.00437
Haiku 4.5 $0.00002 $0.00219

Measured 2d ago against content hash cdeac825ab44, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devteam-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.

skills/devteam-status/SKILL.md · 280 lines

How it starts

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

Session state: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session" Recent events: !sqlite3 .devteam/devteam.db "SELECT type, message FROM events ORDER BY created_at DESC LIMIT 10" 2>/dev/null || echo "No events"

DevTeam Status Command

Command: /devteam:status [options]

Display system health, current progress, costs, and execution history.

Usage

# Current session status
/devteam:status

# Show execution history
/devteam:status --history
/devteam:status --history 20    # Last 20 sessions

# Cost breakdown
/devteam:status --costs
/devteam:status --costs --detailed

# Agent performance metrics
/devteam:status --agents

# Check specific session
/devteam:status --session session-20260129-123456-abc123

# Show all (comprehensive report)
/devteam:status --all

Options

Option Description
--history [n] Show last n sessions (default: 10)
--costs Show cost breakdown
--detailed Show detailed breakdown (with --costs)
--agents Show agent performance metrics
--session <id> Show specific session details
--all Show comprehensive report
--json Output as JSON

Your Process

Check for Running Session

source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"

if is_session_running; then
    show_current_session_status
else
    show_system_overview
fi

Output: Current Session

DevTeam Status

Session: session-20260129-103045-a1b2c3
Started: 2026-01-29 10:30:45 (23 min ago)
Command: /devteam:implement --sprint 1

Progress
  Sprint: SPRINT-001 (Add user authentication)
  Tasks:  60% (3/5 complete)

  Current Task: TASK-004 - Implement JWT middleware
    Agent: backend:api-developer-typescript
    Model: sonnet (escalated from haiku)
    Iteration: 3 of 10

Model Usage
  Model    | Runs | Success | Tokens  | Cost
  haiku    |   12 |   83%   |  45,231 | $0.06
  sonnet   |    4 |   75%   |  28,102 | $0.42
  opus     |    1 |  100%   |  15,883 | $2.38
  Total    |   17 |   82%   |  89,216 | $2.86

Quality Gates (Last Iteration)
  Lint          passed
  Type Check    passed
  Tests         2 failing (AuthMiddleware.test.ts)
  Security      pending
  Coverage      pending

Escalations
  10:35  haiku -> sonnet   2 test failures (api_developer)
  10:48  sonnet -> opus    Architecture issue detected
  Total: 2 escalations

Circuit Breaker
  State: CLOSED (healthy)
  Consecutive Failures: 1 of 5
  Bug Council: Not activated

Read the full file on GitHub · 280 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. 2d ago First seen · 280 lines · 0 tokens per session scan A cdeac825ab44

Subscribe to this mod's changes

devteam-status is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 2,187 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.

Related

Other skills, from other repositories

hydra

Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku, Sonnet) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code…

AR6420/Hail_Hydra · 83 tokens

quality-stack

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when…

joaquimscosta/arkhe-claude-plugins · 148 tokens

prototype

Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to…

joaquimscosta/arkhe-claude-plugins · 118 tokens

lyra

Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.

joaquimscosta/arkhe-claude-plugins · 56 tokens

taskfile-setup

Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile…

joaquimscosta/arkhe-claude-plugins · 110 tokens

sops-add-key

Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".

joaquimscosta/arkhe-claude-plugins · 72 tokens