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 skills/tada5hi/skills/generate-commit-messagenpx skills add tada5hi/skills --skill generate-commit-messagegit clone --depth 1 https://github.com/tada5hi/skillsWhat 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.00047 | $0.01079 |
| Opus 5 | $0.00023 | $0.00540 |
| Sonnet 5 | $0.00009 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
generate-commit-message 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-commit-message
Analyze uncommitted changes in the working directory and generate a commit message following the Conventional Commits 1.0.0 specification.
Conventional Commits Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
| Type | When to use |
|---|---|
feat |
A new feature (SemVer MINOR) |
fix |
A bug fix (SemVer PATCH) |
build |
Changes to the build system or external dependencies |
chore |
Maintenance tasks that don't modify src or test files |
ci |
Changes to CI configuration files and scripts |
docs |
Documentation-only changes |
style |
Formatting, whitespace, semicolons — no code logic change |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
A code change that improves performance |
test |
Adding or correcting tests |
Breaking changes
Indicate breaking changes (SemVer MAJOR) by either:
- Adding
!after the type/scope:feat(api)!: remove deprecated endpoint - Adding a
BREAKING CHANGE:footer (must be uppercase)
Step 1: Gather changes
Run these commands to understand the current state:
# Check what's staged vs unstaged
git status --short
# Show staged changes (if any)
git diff --cached --stat
git diff --cached
# Show unstaged changes (if any)
git diff --stat
git diff
# Show untracked files that might be relevant
git ls-files --others --exclude-standard
# Get recent commit messages for style reference
git log --oneline -10
Important:
- If there are no staged changes and no unstaged changes, inform the user there is nothing to commit and stop.
- If there are both staged and unstaged changes, generate the message based on staged changes only (what
git commitwould include). Mention that unstaged changes exist but won't be included. - If nothing is staged but there are unstaged changes, generate the message for all unstaged changes and note that the user will need to stage them first.
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 · 107 lines · 47 tokens per session scan A a5b74caec503
generate-commit-message is a skill published in the GitHub repository tada5hi/skills (2 stars, last pushed 21d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,079 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…