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/dykyi-roman/awesome-claude-code/commitgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/commit)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/commit"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/commit.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.01058 |
| Opus 5 | $0.00018 | $0.00529 |
| Sonnet 5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
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 today.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Commit & Push
You are a git commit specialist that creates meaningful commit messages.
Input Parsing
Parse $ARGUMENTS to extract tag name and optional meta-instructions:
Format: [tag-name] [-- <meta-instructions>]
Examples:
- /acc:commit
- /acc:commit v2.5.0
- /acc:commit -- focus on security changes
- /acc:commit v2.5.0 -- mention breaking changes
- /acc:commit -- use Russian for commit message
Parsing rules:
- Split
$ARGUMENTSby--(space-dash-dash-space) - First part = tag name (optional, version tag to create)
- Second part = meta-instructions (optional, commit message hints)
If meta-instructions provided, use them to:
- Focus commit message on specific aspects
- Use specific language for message
- Highlight specific types of changes
- Add specific context to commit message
Process
1. Check for changes
Run git status to see if there are any changes to commit.
If no changes exist (working tree clean), respond: "No changes to commit. Working tree is clean."
2. Stage changes
- If there are staged changes, use them
- If nothing is staged but there are unstaged changes, run
git add -Ato stage all
3. Analyze changes
Run git diff --staged to see what will be committed.
Analyze the diff to understand:
- What type of change: feat/fix/refactor/docs/test/chore/perf/style/ci/build
- What was changed
- Why it matters
4. Review recent commits
Run git log -5 --oneline to understand the project's commit message style.
5. Generate commit message
Create a commit message following this format:
type(scope): brief summary in lowercase (max 50 chars)
- Detailed explanation of what changed
- Why the change was made
- Any important context
Types:
- feat: new feature
- fix: bug fix
- refactor: code restructuring
- docs: documentation
- test: tests
- chore: maintenance, dependencies
- perf: performance improvement
- style: formatting, whitespace
- ci: CI/CD configuration
- build: build system, dependencies
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.
- today First seen · 160 lines · 0 tokens per session scan A 6300602056d5
commit is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 36 tokens to every session and 1,058 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
ship
릴리즈 엔지니어링. atomic commit 분리 + 릴리즈 노트 자동 생성 + 태그. 'ship', '릴리즈', '배포 커밋', 'release' 요청 시 사용.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
changelog
Automatic changelog generation. Produces a structured changelog from commit history.
stable
Command "stable" from ruizrica/toolkit, covering /stable, usage, arguments, how it works and what gets created.