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/PacktPublishing/Agentic-Coding-with-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/packtpublishing/agentic-coding-with-claude-code/commit-code)<a href="https://agentmods.dev/commands/packtpublishing/agentic-coding-with-claude-code/commit-code"><img src="https://agentmods.dev/badge/commands/packtpublishing/agentic-coding-with-claude-code/commit-code.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.1 | $0.00000 | $0.00053 |
| Opus 5 | $0.00000 | $0.00026 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
commit-code 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.
What it actually says
Commit Code
Review the files that have changed, and create a commit with a commit message summrizing the changes made. Always try to give short and concise messages that convey the buisness logic.
Use user hints to be the message main subject $arguments
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 · 6 lines · 0 tokens per session scan A 9a70dd92cf39
commit-code is a command published in the GitHub repository PacktPublishing/Agentic-Coding-with-Claude-Code (186 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 53 tokens. 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-04.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.