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 CrypticSwarm/Swarmforge --skill commit-messagesgit clone --depth 1 https://github.com/CrypticSwarm/SwarmforgeWrote 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/crypticswarm/swarmforge/commit-messages)<a href="https://agentmods.dev/skills/crypticswarm/swarmforge/commit-messages"><img src="https://agentmods.dev/badge/skills/crypticswarm/swarmforge/commit-messages/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/crypticswarm/swarmforge/commit-messages"><img src="https://agentmods.dev/badge/skills/crypticswarm/swarmforge/commit-messages.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.00040 | $0.01478 |
| Opus 5.5 | $0.00016 | $0.00591 |
| Sonnet 5.5 | $0.00008 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Messages
Use this workflow whenever you need to write or review a Git commit message.
Response discipline: When fulfilling this skill, output only the commit message text (subject line plus optional body) and nothing else.
Agent workflow
Aim for messages that help a reviewer (often future you) understand intent.
- Identify the user-visible intent (what changes when applied).
- If the diff includes multiple changes, pick the primary feature/outcome.
- Draft an imperative subject that leads with that primary feature.
- Heuristic:
Verb + user-facing object + benefit
- Heuristic:
- Add a body to capture secondary context (enablers, constraints, risk).
- Ensure the commits in a PR "tell a story" (each subject advances it).
- Re-check for clarity without reading the diff.
Format
Subject line (first line)
- Capitalize the first word.
- Keep it short: aim for 50 characters or less.
- Lead with the primary user-visible feature/outcome.
- Prefer:
Persist session data between runs - Avoid:
Prepare host dirs for Docker run
- Prefer:
- Use the imperative mood (describe what the commit does when applied):
- Good:
Add caching to user lookup - Bad:
Added caching to user lookup - Bad:
Adds caching to user lookup
- Good:
- No trailing period.
Blank line
- Always put a blank line after the subject.
- Omit the body entirely if it adds no value, but keep the blank line rule when a body exists.
Body (optional)
- Wrap paragraphs to ~72 columns.
- Focus on why and impact (rationale, constraints, tradeoffs, risk).
- Use the body for secondary details (enabling work, implementation notes, migration, risk) so the subject can stay feature-first.
- Prefer intent and constraints over a narration of the diff.
- Answer at least one of:
- Why was this necessary?
- What behavior changed (user-visible or system-level)?
- What alternatives were considered and rejected?
- What risks or follow-ups exist?
- Link to relevant context when available (issue/PR/ticket IDs).
- Separate paragraphs with blank lines.
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 · 194 lines · 40 tokens per session scan A 4015721d06cb
commit-messages is a skill published in the GitHub repository CrypticSwarm/Swarmforge (3 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 1,478 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-31.
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.