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/anilcancakir/claude-code/commitgit clone --depth 1 https://github.com/anilcancakir/claude-codeWhat 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.00130 | $0.01989 |
| Opus 5 | $0.00065 | $0.00994 |
| Sonnet 5 | $0.00026 | $0.00398 |
| Haiku 4.5 | $0.00013 | $0.00199 |
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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ac:commit
Commit the current working-tree changes as atomic commits using the ac:git-master skill.
Request: $ARGUMENTS
Phase 0: Parse arguments
- Scan
$ARGUMENTSfor--skip-preflight→SKIP_PREFLIGHT = true | false. - Scan
$ARGUMENTSfor--no-push→NO_PUSH = true | false. - Treat any other tokens as free-form note; ignore for now (the commit-style detection in Phase 2 produces the actual message).
Phase 1: Context
Capture the current git state up front so the rest of the command works from real data, not assumptions.
- Current branch: !
git branch --show-current - Working-tree status: !
git status --short - Staged diff stat: !
git diff --staged --stat - Unstaged diff stat: !
git diff --stat - Recent commits (30 for style detection): !
git log -30 --pretty=format:"%h %s" - Upstream tracking: !
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM" - Merge base with main/master: !
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null || echo "NO_BASE" - Local-only commits ahead of base: !
git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)..HEAD 2>/dev/null || echo "NO_BASE"
If the working tree is clean (status output empty), stop with the message Nothing to commit. Working tree clean. and skip every remaining phase.
Phase 2: Preflight (skip if SKIP_PREFLIGHT)
Goal: Catch obvious breakage before writing history.
Skip this phase when SKIP_PREFLIGHT = true. /ac:execute Phase 4 sets this flag because it already ran the Final Verification Wave; running typecheck and tests a second time wastes time.
When SKIP_PREFLIGHT = false:
- Read
CLAUDE.mdandCLAUDE.local.mdif present to find typecheck, test, and lint commands (sections labelledcommands,scripts, or under a "Build / Test / Lint" header). Fall back topackage.jsonscriptsblock when CLAUDE.md does not name the commands. - Run typecheck, then tests, then linter in that order. Each one through
Bash. Use the project's actual commands, not generic guesses. - Pass: continue to Phase 3.
- Fail: stop. Print which preflight step failed and the first ~30 lines of the failure output. Do not commit. The user fixes the issue and re-invokes
/ac:commit.
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.
- yesterday First seen · 118 lines · 130 tokens per session scan A fa895f996199
commit is a command published in the GitHub repository anilcancakir/claude-code (3 stars, last pushed 13d ago), licensed MIT. It adds 130 tokens to every session and 1,989 once invoked, about $0.0006 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.