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/d-o-hub/github-template-ai-agents/commitgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/commit)<a href="https://agentmods.dev/commands/d-o-hub/github-template-ai-agents/commit"><img src="https://agentmods.dev/badge/commands/d-o-hub/github-template-ai-agents/commit.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 | $0.00004 | $0.00196 |
| Opus 5 | $0.00002 | $0.00098 |
| Sonnet 5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
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.
What it actually says
Create a conventional commit
Use this command to create a valid conventional commit.
Usage
./scripts/ai-commit.sh --type <type> [--scope <scope>] --subject <subject> [--body <body> ...]
Rules
- Type: Must be one of
feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert. - Subject: Max 72 characters, imperative mood, no period at the end.
- Body: Use multiple
--bodyflags for multiple paragraphs. Lines are automatically wrapped at 100 characters.
Manual Commits
If you commit manually, the commit-msg hook will validate your message. If it fails, use git commit --amend to fix it.
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 · 24 lines · 4 tokens per session scan A a32859eaac23
commit is a command published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 196 once invoked, about $0.0000 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-03.
Other commands, from other repositories
implement-issue
You are orchestrating a Plan → Implement → Review → Remediate → PR cycle for a GitHub issue, with support for stacked PRs when issues form a linear dependency chain.
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
quick-commit
Create a conventional commit with an auto-generated message.
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
fest-commit
Commit changes with festival traceability metadata.
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…