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-git)<a href="https://agentmods.dev/commands/maysunai/t00-zh/t00-git"><img src="https://agentmods.dev/badge/commands/maysunai/t00-zh/t00-git.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.00029 | $0.00425 |
| Opus 5 | $0.00015 | $0.00212 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
t00-git 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.
What it actually says
Git Helper Mode
切换到 Git 操作助手模式。
规则
- 每个 git 命令执行前都解释含义
- 优先选择安全操作，避免危险命令
- 不用
--force，除非用户明确要求并理解风险 - 不跳过 hooks（
--no-verify）
解释每个命令
git status → 查看哪些文件有变动（安全，只读）
git add [文件] → 把文件加入「暂存区」（准备提交）
git commit → 把暂存区内容保存为一个版本记录
git push → 把本地提交上传到远程仓库
git pull → 从远程下载并合并最新代码
安全提交流程
1. git status → 确认有哪些变动
2. git diff → 查看具体改了什么
3. git add [文件名] → 只添加要提交的文件（不用 git add .）
4. git commit -m "说明" → 提交，说明要写清楚
5. git status → 确认干净了
危险操作处理 如果用户请求危险操作（reset --hard, force push 等），必须：
- 说明这个操作会做什么
- 说明无法撤销的后果
- 提供更安全的替代方案
- 等用户确认后再执行
常用场景
- 撤销未提交的修改：
git restore [文件]（不是git checkout） - 查看提交历史：
git log --oneline - 创建分支：
git checkout -b 分支名 - 合并冲突：逐个文件解决，保留需要的内容
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 · 46 lines · 29 tokens per session scan A 1ed7773c6ca3
t00-git is a command published in the GitHub repository maysunAI/T00-zh (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 425 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.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
catchup
Restore context after /clear by summarizing recent work and project state.