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/hautc-it/cilWrote 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/hautc-it/cil/commit)<a href="https://agentmods.dev/commands/hautc-it/cil/commit"><img src="https://agentmods.dev/badge/commands/hautc-it/cil/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/hautc-it/cil/commit"><img src="https://agentmods.dev/badge/commands/hautc-it/cil/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.00029 | $0.00312 |
| Opus 5.5 | $0.00012 | $0.00125 |
| Sonnet 5.5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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 1mo 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
Generate and run a commit for staged changes.
Step 1 — Inspect
git diff --staged
git status
Check nothing sensitive is staged: .env, API keys, large binaries, generated files.
If anything suspicious: warn and stop.
Step 2 — Analyze
What changed? Identify:
- Type: feat | fix | refactor | docs | test | chore | perf
- Scope: affected module or area (optional)
- What it adds/fixes/removes — the WHY, not the WHAT
Step 3 — Draft message
Format:
<type>(<scope>): <short description under 72 chars>
<body — only if the why is non-obvious>
Examples:
feat(auth): add OAuth2 login with Google provider
fix(api): return 404 instead of 500 for missing users
refactor(db): extract query builder to reduce duplication
Step 4 — Commit
git commit -m "<message>"
If pre-commit hook fails: fix the issue, re-stage, create new commit (never --no-verify).
Report: "Committed: [message]"
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.
- 1mo ago First seen · 62 lines · 29 tokens per session scan A f062428875e1
commit is a command published in the GitHub repository hautc-it/cil (1 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 312 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
commit
Creates git commits using conventional commit format with appropriate emojis, following project standards and creating descriptive messages that explain the purpose of changes.
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.