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 skills add armanzeroeight/fastagent-plugins --skill commit-message-generatorgit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/skills/armanzeroeight/fastagent-plugins/commit-message-generator)<a href="https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/commit-message-generator"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/commit-message-generator/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/skills/armanzeroeight/fastagent-plugins/commit-message-generator"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/commit-message-generator.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.00031 | $0.01326 |
| Opus 5.5 | $0.00012 | $0.00530 |
| Sonnet 5.5 | $0.00006 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
commit-message-generator 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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Generator
Generate clear, conventional commit messages from git diffs.
Quick Start
Analyze staged changes and generate message:
git diff --staged
# Then generate message following conventional commits format
Instructions
Step 1: Analyze Changes
Review the git diff to understand:
- What files changed
- What functionality was added/modified/removed
- Scope of changes (component, module, feature)
- Breaking changes or deprecations
git diff --staged
# or for specific files
git diff --staged path/to/file
Step 2: Determine Commit Type
feat: New feature
- Adding new functionality
- New user-facing capability
- New API endpoint
fix: Bug fix
- Fixing a bug
- Correcting behavior
- Resolving an issue
docs: Documentation
- README updates
- Code comments
- API documentation
style: Code style
- Formatting changes
- Missing semicolons
- Whitespace changes
- No code logic changes
refactor: Code refactoring
- Restructuring code
- No functionality change
- Performance improvements
test: Tests
- Adding tests
- Updating tests
- Test infrastructure
chore: Maintenance
- Dependency updates
- Build configuration
- CI/CD changes
- Tooling updates
perf: Performance
- Performance improvements
- Optimization changes
ci: CI/CD
- CI configuration
- Build scripts
- Deployment changes
build: Build system
- Build tool changes
- External dependencies
revert: Revert
- Reverting previous commit
Step 3: Identify Scope
Scope indicates what part of codebase changed:
- Component name:
(button),(navbar) - Module name:
(auth),(api) - Feature area:
(payments),(search) - Package name:
(core),(utils)
Optional but recommended for clarity.
Step 4: Write Description
Subject line (first line):
- Use imperative mood ("add" not "added")
- No period at end
- Max 50-72 characters
- Lowercase after type
- Clear and concise
Body (optional, after blank line):
- Explain what and why, not how
- Wrap at 72 characters
- Use bullet points for multiple changes
- Reference issues/tickets
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 · 284 lines · 31 tokens per session scan A 336db188baee
commit-message-generator is a skill published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 1,326 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-09-03.
Other skills, from other repositories
adk-git
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
git-github-workflow
A guide for collaborating on code with Git and GitHub. Git tracks changes locally, while GitHub hosts repositories and supports pull requests, reviews, and team workflows.
chinese-commit-conventions
A Chinese-language reference for writing commit messages and changelogs, which record code changes and releases.
hook-safety-review
Use when a hook is about to be enabled or modified -- a hook recipe proposed for activation, a pre/post-tool or lifecycle hook added to agent settings, a git pre-commit hook added to a repo, or a third-party hook snippet pasted in from outside.