Borrowing it
Nothing to install: this file belongs to sumulige/sumulige-claude. 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/sumulige/sumulige-claude/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/sumulige/sumulige-claudeWrote 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/sumulige/sumulige-claude/commit)<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/commit"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/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/sumulige/sumulige-claude/commit"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/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.00008 | $0.00314 |
| Opus 5.5 | $0.00003 | $0.00126 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 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.
What it actually says
Create a git commit following best practices.
Step 1: Assess Current State
Run these commands in parallel:
git status
git diff
git log -5 --oneline
Step 2: Stage Changes
- Review what files are changed
- Ask user if all changes should be committed, or if some should be staged separately
- Never commit these patterns:
.env,.env.local, credentialsnode_modules/,dist/,build/.DS_Store,*.log- Any API keys, tokens, or secrets
Step 3: Write Commit Message
Follow this format based on change type:
| Type | Usage |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style changes (formatting) |
refactor |
Code refactoring |
test |
Adding or updating tests |
chore |
Build process, tooling |
Commit message template:
<type>: <brief description (50 chars max)>
<detailed explanation if needed>
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Step 4: Create Commit
Use git commit with the message, then run git status to confirm.
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 · 54 lines · 8 tokens per session scan A b8e6aecffb49
commit is a command published in the GitHub repository sumulige/sumulige-claude (1 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 314 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
add-to-changelog
Add a new entry to the project's CHANGELOG.md file following Keep a Changelog format.
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
commit
A command that checks staged Git changes and creates a commit from them.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
afrv
Revise the current feature worktree after code review — decide accept/revert/modify (shortcut for feature-code-revise).