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-estimate)<a href="https://agentmods.dev/commands/maysunai/t00-zh/t00-estimate"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-estimate/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-estimate"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-estimate.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.00031 | $0.00320 |
| Opus 5 | $0.00015 | $0.00160 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
t00-estimate 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-estimate $ARGUMENTS」时，根据 $ARGUMENTS 决定模式：
模式1：开始前预估（$ARGUMENTS 含「开始」「实现」「做」）
输出格式：
需求可达性评估：
- 核心功能：✅ 可实现（约X小时）
- 功能A：✅ 可实现
- 功能B：⚠️ 需确认（依赖第三方 API，可能有限制）
- 功能C：❌ 当前技术栈难实现
预估完成度：85%
规则：
- ≥ 90%：直接开始实现
- 70–89%：说明限制，问用户是否继续
- < 70%：先讨论，给出替代方案，不直接做
模式2：完成后报告（$ARGUMENTS 含「完成了吗」「做完了」「报告」）
输出格式：
需求完成报告：
✅ 功能A — 完成
✅ 功能B — 完成
⚠️ 功能C — 部分完成（原因）
❌ 功能D — 未完成（原因）
总完成度：X / Y 项（XX%）
模式3：无参数
列出当前项目或当前任务的预估状态。
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 · 31 tokens per session scan A 9ce138ba1bf2
t00-estimate is a command published in the GitHub repository maysunAI/T00-zh (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 320 once invoked, about $0.0002 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.