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/koolamusic/claudefiles/gitcommitgit clone --depth 1 https://github.com/koolamusic/claudefilesWhat 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.00011 | $0.00831 |
| Opus 5 | $0.00005 | $0.00415 |
| Sonnet 5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
gitcommit 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Staged changes: !
git diff --cached --stat - Unstaged changes: !
git diff --stat - Full diff: !
git diff HEAD - Recent commits: !
git log --oneline -5
Your task
- Check if there are changes to commit; if none, inform the user and stop
- Review the diff for sensitive data (API keys, passwords, .env files) — warn if found
- Analyze changes to understand the nature and purpose
- Generate 3 commit message candidates per the Message format section below
- Present candidates to the user and ask which to use (or suggest edits)
- Stage unstaged changes if user confirms
- Execute
git commitwith the selected message - If pre-commit hooks fail, report the error and offer to fix
Message format
Conventional Commits. Why over what — the diff already shows what changed. Match project convention (use the recent-commits context above to detect capitalization, scope style, and trailer usage).
Subject line
- Format:
<type>(<scope>): <imperative summary>— scope optional - Append
!after type/scope to mark a breaking change:feat(api)!:orfeat!: - Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
- ≤50 chars when possible, hard cap 72
- No trailing period
Types
feat— new featurefix— bug fixrefactor— code restructuring without behavior changeperf— performance improvementdocs— documentationtest— testschore— maintenance, tooling, depsbuild— build system, packagingci— CI configurationstyle— formatting, whitespacerevert— reverts a prior commit
Body
- Skip when the subject is self-explanatory
- Add when the why isn't obvious from the diff
- Wrap at 72 chars; bullets
-not* - Reference issues/PRs at end as trailers:
Closes #42,Refs #17
Mandatory body (regardless of how obvious it seems): breaking changes, security fixes, data migrations, reverts.
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 · 100 lines · 11 tokens per session scan A b4e7ac2fc5ed
gitcommit is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 831 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.
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.