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/thapaliyabikendra/ai-artifacts/generate-commit-msggit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWhat 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.00285 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
generate-commit-msg 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
Generate Commit Message
Generate conventional commit message from staged changes.
Arguments
$ARGUMENTS: [--full] [--scope <scope>] [--type <type>]
| Argument | Default | Description |
|---|---|---|
--full |
off | Include markdown body with summary and changes |
--scope |
auto | Override scope (e.g., api, ui, docs) |
--type |
auto | Override type (e.g., feat, fix, refactor) |
Workflow
- Run
git diff --staged— if empty, tell user to stage files first - Analyze changes and generate message in format:
<type>(<scope>): <summary>
Output Format
Quick Mode (default):
<type>(<scope>): <summary>
Full Mode (--full):
<type>(<scope>): <summary>
<Brief summary of what changed and why>
- <change 1>
- <change 2>
Constraints
- Max 72 characters for title
- No emojis, no markdown in title
CRITICAL: Output ONLY the raw commit message. No explanations, no analysis, no "Here's the message:", no code blocks. Just the message text itself.
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 · 43 lines · 0 tokens per session scan A 85bd9de847eb
generate-commit-msg is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 285 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-30.
Other commands, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
智能生成 Git 提交信息并提交.
commit
Create a Conventional Commit with signoff.