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/maysunAI/T00-zhWrote 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/maysunai/t00-zh/t00-status)<a href="https://agentmods.dev/commands/maysunai/t00-zh/t00-status"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-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/maysunai/t00-zh/t00-status"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-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.00028 | $0.00304 |
| Opus 5 | $0.00014 | $0.00152 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
t00-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 10d 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
用户说「/t00-status」时，输出当前状态报告：
Step 1：文件状态
读取并统计：
temp01_req.md→ 总行数，最后有效内容行temp03_reply.md→ 总行数，最后一个 ══════ 块的位置
Step 2：任务状态
读取 F:\T00\tasks\TASK_INDEX.md，列出「进行中 🔄」和「待处理 📋」的任务（高优先级优先）。
Step 3：RESUME 摘要
读取 F:\T00\RESUME.md，提取「下一步」部分。
输出格式
=== T00 当前状态 ===
📄 通信文件
req: XX 行（最后处理到第XX行）
reply: XX 行（最后区块第XX行）
🔄 进行中任务
T015 PJ11 Phase 2-6
T018 任务化系统
📋 待处理（高优先）
T033 AI00发布到GitHub
T036 T00/T00-zh 发布
📌 上次会话下一步
（RESUME.md 下一步内容）
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.
- 10d ago First seen · 42 lines · 28 tokens per session scan A c90ae74bfdb0
t00-status is a command published in the GitHub repository maysunAI/T00-zh (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 304 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-31.
Other commands, from other repositories
epic-claim
Claim an epic issue, stamp coordination state, and sync local ownership.
epic-decompose
Break an epic into task children without creating task branches.
epic-publish
Publish a validated epic update back to the issue and local cache.
epic-review
Mark epic review requested, approved, or changes requested.
epic-sync
Sync epic issue bodies, labels, and local coordination snapshots from GitHub.
epic-unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.