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/hmj1026/dhpkWrote 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/hmj1026/dhpk/smart-commit)<a href="https://agentmods.dev/commands/hmj1026/dhpk/smart-commit"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/smart-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/hmj1026/dhpk/smart-commit"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/smart-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.00019 | $0.00371 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
smart-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 3d 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
- Status: !
git status --short - Recent style: !
git log --oneline -10 - Branch: !
git rev-parse --abbrev-ref HEAD
Task
Follow the git-smart-commit skill workflow:
- Detect mode: Read CLAUDE.md / execution-policy "Git pipeline" → manual or auto
- Pre-flight: Verify
/precommitpassed for code changes - Collect:
git status,git diff --stat, exclude sensitive files - Group: High-cohesion grouping (staged first, then by feature/type)
- Generate: Commit messages matching project style + git commands
- Verify:
git statusafter user executes
Arguments:
--scope <path>: Only include changes under this path--type <type>: Force all commits to use this type (feat/fix/docs/etc.)--ai-co-author: AddCo-Authored-By: Claude <[email protected]>trailer to commit messages (off by default)
Output
For each commit group, output a code block with copy-pasteable git commands.
Respect rules/execution-policy.md "Git pipeline" — if Claude is forbidden from git commit, output commands only.
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.
- 3d ago First seen · 36 lines · 19 tokens per session scan A 2b6c8a29ccec
smart-commit is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 371 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-09-05.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
commit
Create well-formatted commits with conventional commit messages and emojis.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.