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.
npx agentmods add commands/kinopeee/cursorrules/commit-onlygit clone --depth 1 https://github.com/kinopeee/cursorrulesWhat 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 | $0.00000 | $0.00543 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
commit-only 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 2d 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
コミットのみ（現在のブランチ）
概要
現在のブランチに対して、ローカルの変更をコミットだけ行うためのシンプルなコマンドです。
リモートへのプッシュやブランチ戦略（main 直コミット禁止など）は扱わず、コミットメッセージ規約に沿ったコミットだけを行います。
前提条件
- 変更済みファイルが存在すること
- コミットメッセージの具体的な書き方は、
.cursor/rules/commit-message-format.mdcなどで定義された規約に従うこと
実行手順（対話なし）
- 未コミット差分を確認し、コミットメッセージの内容を検討する（例：
git diffやgit diff --cached） - 変更のステージング（
git add -A） - コミット（環境変数または引数でメッセージを渡す）
A) 安全な一括実行（メッセージ引数版）
MSG="<Prefix>: <サマリ（命令形/簡潔に）>" \
git add -A && \
git commit -m "$MSG"
例：
MSG="fix: 不要なデバッグログ出力を削除" \
git add -A && \
git commit -m "$MSG"
B) ステップ実行（読みやすさ重視）
# 1) 差分を確認
git status
git diff
# 2) 変更をステージング
git add -A
# 3) コミット（メッセージを編集）
git commit -m "<Prefix>: <サマリ（命令形/簡潔に）>"
ノート
- コミットメッセージのフォーマットやメッセージ生成の原則は、
.cursor/rules/commit-message-format.mdcのルールに従ってください。 - ブランチ戦略（例：main 直コミット禁止、作業用ブランチ運用）やリモートへのプッシュ (
git push) は、このコマンドの対象外です。必要に応じて、プロジェクトごとの README / CONTRIBUTING / 別コマンドで定義してください。
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.
- 2d ago First seen · 55 lines · 0 tokens per session scan A a8ae2c549e24
commit-only is a command published in the GitHub repository kinopeee/cursorrules (1,116 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.