A status command for AgenTeam, a system that coordinates several work stages and roles on a coding task. It shows what is running, completed, waiting, or blocked.

Use it to check pipeline stages, active work locks, verification attempts, recent events, elapsed time, and remaining run time.

It gives you one view of a task's progress instead of requiring you to inspect separate logs or guess which stage is active.

status — Skill for Claude Code and Codex by yimwoo/codex-agenteam

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 yimwoo/codex-agenteam --skill status

Clone the repo

git clone --depth 1 https://github.com/yimwoo/codex-agenteam

Made for: Claude Code, Codex.

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/yimwoo/codex-agenteam/status/github.svg)](https://agentmods.dev/skills/yimwoo/codex-agenteam/status)

Your own site

<a href="https://agentmods.dev/skills/yimwoo/codex-agenteam/status"><img src="https://agentmods.dev/badge/skills/yimwoo/codex-agenteam/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/yimwoo/codex-agenteam/status"><img src="https://agentmods.dev/badge/skills/yimwoo/codex-agenteam/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 580 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.00020	$0.00580
Opus 5.5	$0.00008	$0.00232
Sonnet 5.5	$0.00004	$0.00116
Haiku 4.5	$0.00002	$0.00058

Measured 1mo ago against content hash 74b5808963f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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/status/SKILL.md · 75 lines

How it starts

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

AgenTeam Status

Display the current state of the team's work.

Process

1. Get Status

Use the --progress flag for a compact, human-friendly view:

python3 <runtime>/agenteam_rt.py status --progress

If the user specifically asks for raw JSON state, use without --progress:

python3 <runtime>/agenteam_rt.py status

2. Format Output

Display the progress view in a readable format:

AgenTeam Run: <run-id>
Task: <task description>
Profile: <profile or "full">
Status: <running|completed|failed|stopped>
Elapsed: <Nm Ss>

Stages:
  research   ✓ completed  (0m 45s)
  strategy   ✓ completed  (0m 30s)
  design     ✓ completed  (1m 02s)
  implement  → verifying   (1m 15s)  [verify attempt 2/3]
  test       · pending
  review     · pending

Active Lock: dev
Last Event: stage_verified (implement) — fail, attempt 2
Attempt: implement-dev-a1 | thread_id: <codex-thread-id>
Last heartbeat: 12s ago | idle budget: 14m 48s remaining
Wall budget: 47m remaining | stop reason: (none)

The progress view includes elapsed times per stage, the current verify attempt if applicable, and the most recent event for context. When governance.adoption is present, include the high-signal governance items in the readable status: open follow-ups/escalations, recorded tripwire blocks or warnings, gate rejections, and criteria overrides. Do not ask the user to inspect raw .agenteam/governance files for these summary facts. For an active or interrupted attempt, always include thread_id (or "unavailable"), last heartbeat and age, idle budget and wall budget remaining, attempt/retry counts, PID liveness when known, and stop reason. Treat a stale heartbeat as AT RISK, not as proof that the role failed.

3. No Active Run

If no run is found, show:

Team config status (does .agenteam/config.yaml or legacy agenteam.yaml exist?)
Available roles
Suggestion: "Use $ateam:run to start a new task."

Symbols

✓ — completed
→ — in progress
· — pending
✗ — failed/blocked

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

1mo ago First seen · 75 lines · 20 tokens per session scan A 74b5808963f3

Subscribe to this mod's changes

status is a skill published in the GitHub repository yimwoo/codex-agenteam (14 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 580 once invoked, about $0.0001 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-30.

LLM Multi-Agent Project management ai-agents codex developer-tools openai

linear-tickets

Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.

langchain-ai/open-swe · 44 tokens

commonly

You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…

Team-Commonly/commonly · 0 tokens

status