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/wesleysmits/agent-skills/commit-message-formatternpx skills add WesleySmits/agent-skills --skill commit-message-formattergit clone --depth 1 https://github.com/WesleySmits/agent-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.00045 | $0.01306 |
| Opus 5 | $0.00023 | $0.00653 |
| Sonnet 5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
formatting-commit-messages 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 212 lines · 45 tokens per session scan A 9390e4197ca2
formatting-commit-messages is a skill published in the GitHub repository WesleySmits/agent-skills (6 stars, last pushed 7mo ago), with no licence file. It adds 45 tokens to every session and 1,306 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
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.
validate-context-routes
Validate that literal project-relative paths referenced by a project's root AGENTS.md exist. Use when changing AGENTS.md routing, moving shared documentation or .agents resources, or checking a dotagents example.
commit-messages
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.
open-source-quality
Use this skill before committing, pushing, or opening a PR. Triggers on phrases like "commit", "git commit", "push", "open PR", "create pull request", "finalize this change". Enforces conventional commit messages, atomic commits, code style (ruff/mypy), public-API docstrings, actionable error messages, changelog…
conventional-commit
Enforces Conventional Commits format for the EndogenAI Workflows repository. USE FOR: composing commit messages (type(scope): description format); reviewing commit message format before push; understanding allowed types (feat/fix/docs/chore/test/refactor/ci/perf) and scopes…