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/echoVic/blade-codeWrote 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/echovic/blade-code/commit)<a href="https://agentmods.dev/commands/echovic/blade-code/commit"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/commit/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/echovic/blade-code/commit"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/commit.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.00008 | $0.00227 |
| Opus 5.5 | $0.00003 | $0.00091 |
| Sonnet 5.5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
commit 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 1mo 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 提交。
当前状态
!`git status --short`
变更详情
!`git diff --cached --stat`
要求
- 分析暂存区的变更，理解修改的目的
- 生成符合 Conventional Commits 规范的提交信息
- 提交信息格式：
type(scope): description - 常用 type：feat, fix, docs, style, refactor, test, chore
- 如果用户提供了额外说明，请结合考虑：$ARGUMENTS
示例
feat(auth): 添加用户登录功能
fix(api): 修复分页参数解析错误
docs(readme): 更新安装说明
请先展示你计划的提交信息，等我确认后再执行 git commit。
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.
- 1mo ago First seen · 41 lines · 8 tokens per session scan A a9ed1028ca11
commit is a command published in the GitHub repository echoVic/blade-code (181 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 227 once invoked, about $0.0000 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
commit
Based on the above changes, create a single git commit.
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
commit-push-pr
Commit, push, and open a PR.
commit
A command for submitting a change, with an optional argument supplied through $ARG.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit
Create well-structured git commits with meaningful messages.