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/design-and-deliver/claude-code-autoconfig/check-commitgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWhat 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.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
check-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.
What it actually says
Commit Reminder Rules
Check if there are uncommitted changes that should be committed, based on these thresholds:
Thresholds:
- >5 uncommitted files OR
- >500 lines changed OR
- Changes older than 24 hours (check last commit time)
Actions:
- Run
git status --shortto see uncommitted files - Run
git diff --statto see lines changed - Run
git log -1 --format="%cr"to see when last commit was made - Count modified/new files and total lines changed
- If any threshold is exceeded:
- Show the stats clearly
- Strongly recommend running
/commit-and-push - Explain which threshold(s) were exceeded
When to check (proactively):
- At the start of each session
- After completing major tasks
- Before starting new work
Note: This command can be run manually anytime to check commit status, or Claude should run it proactively based on the triggers above. The automated companion is the Stop-hook reminder in .claude/settings.json, which fires on its own at higher thresholds (>10 files / >1000 lines) and stays quiet while any session is mid-commit (see .claude/hooks/mark-commit-active.js).
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 · 31 lines · 0 tokens per session scan A 08e66916a930
check-commit is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 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-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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.