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.
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/commit)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/commit"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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/khaledsaeed18/dotclaude/commit"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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.00077 | $0.00581 |
| Opus 5.5 | $0.00031 | $0.00232 |
| Sonnet 5.5 | $0.00015 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
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 24d 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
Context
Hint: $ARGUMENTS
Status:
!git status --short 2>/dev/null | head -40
Branch and recent style:
!git branch --show-current 2>/dev/null; git log --oneline -8 2>/dev/null
Staged and unstaged summary:
!git diff --staged --stat 2>/dev/null | tail -5; echo '---'; git diff --stat 2>/dev/null | tail -5
Task
Apply the git-commit skill end to end for exactly one commit. In short:
- Read the actual diffs (
git diff,git diff --staged). Do not commit what you have not read. - Find and obey the repo's rules: commitlint config, pre-commit or husky hooks, CONTRIBUTING, the message style visible in the log above.
- If the changes contain more than one logical unit, propose the split and commit only the first unit (or the one the hint names); say what remains.
- Stage files explicitly by path. Never
git add -Aorgit add .. Never stage generated output, secrets, or dependencies; flag anything untracked that should be ignored. - Write the message: conventional type and scope matching the repo's convention, subject in the imperative under 72 characters, a body that explains why and what a reviewer needs to know. No AI or co-author mentions of any kind.
- Show the file list and the full message, then ask for a yes before running
git commit. If a hook fails, fix the cause and retry; never--no-verify. - Report the commit hash and subject. Do not push; that is
/pror an explicit request.
If there is nothing to commit, say so and stop.
Inspired by
The role and scope follow the commit-commands plugin's /commit command in Anthropic's claude-code repository. That repository is not open-licensed, so nothing is copied from it; every line here was written for this registry.
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.
- 24d ago First seen · 42 lines · 77 tokens per session scan A f4f479e054fa
commit is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 581 once invoked, about $0.0003 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-09-22.
Other commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
commit
Create a commit with validation (lint + tests) — optionally pass the message.
done
Finalize changes — quick review + check + commit.
push
Send commits to the remote.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.