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 jordantplows/claude-skills --skill commit-writergit clone --depth 1 https://github.com/jordantplows/claude-skillsWrote 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/jordantplows/claude-skills/commit-writer)<a href="https://agentmods.dev/skills/jordantplows/claude-skills/commit-writer"><img src="https://agentmods.dev/badge/skills/jordantplows/claude-skills/commit-writer.svg" alt="Measured on agentmods" 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.01647 |
| Opus 5 | $0.00028 | $0.00823 |
| Sonnet 5 | $0.00011 | $0.00329 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
commit-writer 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 7d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit-writer
Generates proper conventional commit messages from staged changes.
Instructions
-
Check what's staged
git diff --staged --statIf nothing is staged, inform the user and exit.
-
Read the actual changes
git diff --stagedIf the diff is very large (>500 lines), sample key files instead:
git diff --staged --stat git diff --staged path/to/key/file.ts -
Read recent commit history for style
git log --oneline -10 git log -1 --format="%B"This shows the repository's commit message conventions.
-
Determine the commit type
- feat: new functionality added
- fix: bug fix
- refactor: restructuring without behavior change
- chore: tooling, config, dependencies, build setup
- docs: documentation only
- test: test additions or changes
- perf: performance improvement
- style: formatting only, no logic change
If changes span multiple types, pick the dominant one and mention others in the body.
-
Write the subject line Format:
type: short imperative summary- Under 72 characters
- No period at the end
- Imperative mood ("add", "fix", "merge" — not "added", "fixed", "merged")
- Be specific but concise
-
Decide if body is needed
Skip the body for:
- Typo fixes
- Single small bug fixes
- Dependency bumps
- Self-explanatory one-liners
Write a full body for:
- Structural changes
- Multi-file refactors
- New features
- Anything that changes behavior
- Anything where "why" isn't obvious from "what"
-
When writing a body
Structure:
First paragraph: what changed and why, in plain English. Changes: - Group related changes logically - Use bullet points for clarity - Include file paths or component names Updated: - List modified existing features - Explain impact on behavior Renamed: - Old → new mappings - Explain why renamed
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.
- 7d ago First seen · 257 lines · 55 tokens per session scan A 1c74d021596e
commit-writer is a skill published in the GitHub repository jordantplows/claude-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,647 once invoked, about $0.0003 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
010108-version-control
Conventional commit format, git staging safety, disaster recovery with git reflog, and commit message best practices.
review-gate
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met.
clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.