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-publish)<a href="https://agentmods.dev/commands/maysunai/t00-zh/t00-publish"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-publish/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-publish"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-publish.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.00021 | $0.00385 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
t00-publish 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 11d 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-publish $ARGUMENTS」时，执行发布流程（$ARGUMENTS = 项目编号，如 pj90 或 t00）：
-
确定来源和目标
- 根据 $ARGUMENTS 查
PROJECTS_INDEX.md找项目路径 - 对应 github-pub 目录：
F:\T00\PJ02_publish\[对应名称]\
- 根据 $ARGUMENTS 查
-
选择可发布文件（严格排除以下内容）
- ❌
temp0*.mdRESUME.mdREQ_STATUS.md（临时/个人） - ❌
.env*.keycredentials.jsontoken.json（密钥） - ❌
node_modules/__pycache__/.git/（构建产物） - ❌
Z01_archive/Z02_personal/（存档/个人） - ✅ 代码文件、README.md、package.json、设计文档
- ❌
-
复制到暂存区
-
验证清单
- 无绝对路径（
F:\T00等） - 无 API Key / 密码（grep 检查）
- README.md 存在且有内容
- .gitignore 存在
- 无绝对路径（
-
报告给用户
- 列出：复制了哪些文件、排除了哪些、发现的问题
- 询问：「确认后推送 GitHub，还是继续修改？」
-
等用户确认后才执行
git push
⚠️ 未经用户确认，不推送 GitHub。
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.
- 11d ago First seen · 34 lines · 21 tokens per session scan A 5ef315b274f5
t00-publish is a command published in the GitHub repository maysunAI/T00-zh (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 385 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
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
lfe-archivist
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
skill-create
Generate skills from git history analysis.