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.
git clone --depth 1 https://github.com/CronusL-1141/AI-companyWrote 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/commands/cronusl-1141/ai-company/os-status)<a href="https://agentmods.dev/commands/cronusl-1141/ai-company/os-status"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-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.
<a href="https://agentmods.dev/commands/cronusl-1141/ai-company/os-status"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-status.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00279 |
| Opus 5.5 | $0.00009 | $0.00112 |
| Sonnet 5.5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
os-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.
What it actually says
/os-status — 系统状态概览
- 整体概览：
project_summary()（不传参即当前活跃项目）。 - 单支队：
team_status(team_id)。默认返回 compact 投影，那是有意裁剪不是字段缺失。 - 活跃会议：
meeting_list(status="active")。
不要按"遍历团队再逐队 agent_list"的方式拼状态：实测单支队有过 173 个成员，全量摘要
170,331 字符，超出 MCP 返回上限；拿被截断的结果作答，会把一支 173 人的队报成 3 人。
team_status 的投影就是为这次事故做的。
别误诊
- 没有团队是正常的，不需要任何初始化命令：团队由 SubagentStart hook 在第一次派工时 自动建，空列表只说明还没派过子 agent。
- API 不可达时才提示用户走
/os-up。端口见 OS 数据目录的api_port.txt（aiteam paths可查）。
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.
- 2d ago Changed 7d4ff40b6f69
- 1mo ago Changed · -27 lines · +4 tokens per session 58ed2fb91b4a
- 2mo ago First seen · 48 lines · 19 tokens per session scan A 869b765b2c48
os-status is a command published in the GitHub repository CronusL-1141/AI-company (375 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 279 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.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
exec-plan
Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.
gsd-plan-phase
Create detailed phase plan (PLAN.md) with verification loop.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase.