Borrowing it
Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/j5ik2o/event-store-adapter-js/main/.agents/commands/git-commit.mdgit clone --depth 1 https://github.com/j5ik2o/event-store-adapter-jsWrote 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/j5ik2o/event-store-adapter-js/git-commit)<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/git-commit"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/git-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/j5ik2o/event-store-adapter-js/git-commit"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/git-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.00014 | $0.00528 |
| Opus 5.5 | $0.00006 | $0.00211 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
git-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.
This is a copy
100% identical to git-commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
意味のある変更単位ごとにコミットを行うことは、コードの履歴を明確にし、将来の変更を追跡しやすくするために重要です。
以下の手順に従って、ワーキングディレクトリでの変更をコミットします。
0. 直近のコミットを確認する
直近にてどのようにコミットされているかを確認する
git log --oneline
これにより、最近のコミットの一覧が表示され、コミットメッセージとハッシュが確認できます。
1. 変更を確認する
まず、現在のワーキングディレクトリでの変更を確認します。以下のコマンドを実行してください：
git status
2. 変更をステージングする
変更をコミットする前に、ステージングエリアに追加する必要があります。以下のコマンドを使用して、すべての変更をステージングします：
git add 対象ファイルやディレクトリ
意味のある変更単位ごとにファイルを指定すること。無条件にすべての変更を追加しないでください。
3. コミットメッセージを作成する
コミットメッセージは、変更内容を簡潔に説明する重要な部分です。以下のコマンドを使用して、コミットを作成します：
git commit -m "コミットメッセージをここに入力"
- コミットメッセージはConventional Commitsに従い、英語で記述してください。
- co-authorやコミットメッセージに"Claude Code"などのエージェント名は含めないこと。
4. コミットを確認する
コミットが正しく行われたかを確認するために、以下のコマンドを実行します：
git log --oneline
これにより、最近のコミットの一覧が表示され、コミットメッセージとハッシュが確認できます。
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 · 57 lines · 14 tokens per session scan A f104e8245ea0
git-commit is a command published in the GitHub repository j5ik2o/event-store-adapter-js (25 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 528 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-commit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
review-pr
../../.cratis/ai/prompts/review-pr.prompt.md.
ship-changes
../../.cratis/ai/prompts/ship-changes.prompt.md.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
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.