genshijin-commit

A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.

In plain words
What is it for?
Generate a subject of up to 50 characters and an optional body for the current staged changes.
Why use it?
Writing consistent commit messages takes time and can lead to vague descriptions. This command focuses the message on the staged changes and their non-obvious reasons.

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/interfacex-co-jp/genshijin/genshijin-commit
Clone the repo
git clone --depth 1 https://github.com/InterfaceX-co-jp/genshijin
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 84 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.00016 $0.00084
Opus 5 $0.00008 $0.00042
Sonnet 5 $0.00003 $0.00017
Haiku 4.5 $0.00002 $0.00008

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

Security

Grade A, and why

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

commands/genshijin-commit.md · 6 lines

What it actually says

現在のステージング変更に対するコミットメッセージを生成。件名50文字以内、命令形、末尾ピリオドなし。本文は非自明な理由のみ。言語は既存git履歴に合わせる。AI帰属表記禁止。

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 · 6 lines · 16 tokens per session scan A 0216b7a54409

Subscribe to this mod's changes

genshijin-commit is a command published in the GitHub repository InterfaceX-co-jp/genshijin (314 stars, last pushed 17d ago), licensed MIT. It adds 16 tokens to every session and 84 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-30.