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 tahirraufkeeyu/software-development-agent-stack--sdas --skill commit-messagegit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/commit-message)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/commit-message"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/commit-message/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/tahirraufkeeyu/software-development-agent-stack--sdas/commit-message"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/commit-message.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.00055 | $0.01622 |
| Opus 5.5 | $0.00022 | $0.00649 |
| Sonnet 5.5 | $0.00011 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
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 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User runs
git addand asks for a commit message. - User pastes a diff and asks "what's a good commit message for this".
- User finishes a task and asks the agent to commit (combine with a separate
committool/skill that actually runs git).
Do not use this skill to write a PR description (longer, audience-different) or a changelog entry (see the documentation skill).
Inputs
- A staged diff (
git diff --cached) or an unstaged diff. If none is provided, fetchgit statusandgit diff --cachedfrom the repo. - Optional: related issue/ticket id, prior commit for context, the branch name if it encodes intent.
Outputs
A commit message with:
- Subject line:
<type>[optional scope][!]: <imperative summary>, <= 72 characters. - Optional body: wrapped at 72 columns, explaining the why, constraints considered, alternatives rejected.
- Optional footers:
Refs: #123,Closes: #123,BREAKING CHANGE: <what>,Co-authored-by: ....
Tool dependencies
- Bash for
git status,git diff --cached,git log -n 20 --oneline(style calibration). - Read/Grep to glance at touched files when the diff alone is ambiguous.
Procedure
- Read the diff. If it is empty, ask for the staged changes or run
git diff --cached. - Calibrate to the repo's style. Run
git log -n 20 --pretty=format:'%s'. If the repo already uses Conventional Commits, match exactly (types, scope format, capitalisation). If not, propose Conventional Commits and follow the user's existing conventions where they conflict. - Classify the change into one type:
feat— a user-facing new capability.fix— a bug fix observable to users or other systems.perf— a change that improves performance without changing behaviour.refactor— internal restructuring, no behaviour change.docs— documentation only.test— tests only.build— build system, dependencies, packaging.ci— CI/CD configuration.chore— maintenance (bumping deps, cleanup) that is neither feat nor fix.revert— reverts a previous commit.
- Pick a scope if the repo uses them. Scope is usually a package, module, or subsystem (
auth,api,billing). Omit the scope entirely rather than invent one. - Write the subject as an imperative phrase starting lowercase after the colon. "Add", "fix", "rename", never "added" or "adds". Cap at 72 characters; aim for <= 50.
- Decide on a body:
- If the diff is a one-liner obvious from the subject, no body.
- Otherwise, a body answering: why is this change needed; what is the approach; what alternatives were considered and rejected; what risks remain.
- Hard-wrap at 72 columns. Separate subject and body with one blank line.
- Add footers:
Refs: #<n>orCloses: #<n>when linked to an issue.BREAKING CHANGE: <description>when the diff removes or alters a public API, wire format, CLI flag, config key, database column, or event shape. Also append!before the colon in the subject.Co-authored-by:when pair programming.
- Never include implementation trivia the commit hash already captures ("changed 3 files", "added 42 lines"). Instead, state the user-visible or contract-level effect.
- Check length and wrap. Return the final message in a single fenced block so the user can paste it directly.
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 · 144 lines · 55 tokens per session scan A f97c21926808
commit-message is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (19 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,622 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.