commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

In plain words
What is it for?
Use it to review staged changes, generate a message describing their purpose, and create the Git commit after you approve it.
Why use it?
It saves time writing a clear summary of changes and keeps commit messages consistent. It asks for confirmation before creating the commit.

Command

Install

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.

agentmods
npx agentmods add commands/echovic/blade-code/commit
Clone the repo
git clone --depth 1 https://github.com/echoVic/blade-code
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00227
Opus 5 $0.00004 $0.00113
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured yesterday against content hash a9ed1028ca11, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.blade/commands/commit.md · 41 lines

What it actually says

请帮我完成一次 Git 提交。

当前状态

!`git status --short`

变更详情

!`git diff --cached --stat`

要求

  1. 分析暂存区的变更,理解修改的目的
  2. 生成符合 Conventional Commits 规范的提交信息
  3. 提交信息格式:type(scope): description
  4. 常用 type:feat, fix, docs, style, refactor, test, chore
  5. 如果用户提供了额外说明,请结合考虑:$ARGUMENTS

示例

feat(auth): 添加用户登录功能
fix(api): 修复分页参数解析错误
docs(readme): 更新安装说明

请先展示你计划的提交信息,等我确认后再执行 git commit

Changes

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.

  1. yesterday First seen · 41 lines · 8 tokens per session scan A a9ed1028ca11

Subscribe to this mod's changes

commit is a command published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 227 once invoked, about $0.0000 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-30.