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.
npx agentmods add skills/yimwoo/codex-agenteam/statusnpx skills add yimwoo/codex-agenteam --skill statusgit clone --depth 1 https://github.com/yimwoo/codex-agenteamWrote 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.
[](https://agentmods.dev/skills/yimwoo/codex-agenteam/status)<a href="https://agentmods.dev/skills/yimwoo/codex-agenteam/status"><img src="https://agentmods.dev/badge/skills/yimwoo/codex-agenteam/status.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00010 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 6d 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.
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.yamlor legacyagenteam.yamlexist?) - Available roles
- Suggestion: "Use
$ateam:runto start a new task."
Symbols
✓— completed→— in progress·— pending✗— failed/blocked
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.
- 6d ago First seen · 75 lines · 20 tokens per session scan A 74b5808963f3
status is a skill published in the GitHub repository yimwoo/codex-agenteam (13 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 580 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.
Other skills, from other repositories
oh-my-dynamic
Multi-agent orchestration engine for complex tasks. Use when you need to break a complex query into subtasks, run them in parallel with a DAG engine, and synthesize results. Triggers on: multi-agent, parallel execution, orchestrate, DAG, decompose task, dynamic workflow.
multi-agent-run
Run a multi-agent workflow on any complex task. One command to decompose, parallelize, and synthesize. Triggers on: run agents, parallel analysis, multi-agent, decompose and run, orchestrate task.
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
pydantic-ai
Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.