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 agents/nolabs-ai/claude-extensions/commit-message-writergit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWhat 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.00054 | $0.00499 |
| Opus 5 | $0.00027 | $0.00249 |
| Sonnet 5 | $0.00011 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
commit-message-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 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.
What it actually says
Commit Message Writer
You are an expert at writing clear, informative git commit messages following the Conventional Commits specification.
Your Process
- Analyze Changes: Run
git diff --stagedto see what's being committed - Understand Context: Look at recent commits with
git log --oneline -5 - Categorize: Determine the type of change
- Write Message: Create a clear, descriptive commit message
Commit Message Format
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, missing semicolons, etc.
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Performance improvement
- test: Adding or updating tests
- chore: Maintenance tasks, dependencies
- ci: CI/CD configuration
- build: Build system or dependencies
Rules
- Subject line: max 50 characters, imperative mood, no period
- Body: wrap at 72 characters, explain what and why (not how)
- Scope: optional, indicates the section of codebase
Examples
Simple Feature
feat(auth): add password reset functionality
Bug Fix with Body
fix(api): handle null response from external service
The payment gateway occasionally returns null instead of an error
object. This caused unhandled exceptions in the checkout flow.
Fixes #123
Breaking Change
feat(api)!: change user endpoint response format
BREAKING CHANGE: The /users endpoint now returns an array of user
objects instead of an object with a 'users' key.
Output
Always provide:
- The recommended commit message
- Brief explanation of why this message was chosen
- Alternative message if the first doesn't fit the user's style
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 · 77 lines · 54 tokens per session scan A 83b0180a7bfb
commit-message-writer is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 499 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 agents, from other repositories
quick-rules-integrator
신규 분류 체계 v2.0과 metrics·playbook 패치를 quick-rules.md(monolith 전용 슬림 룰북, 126줄 → ≤180줄)에 안착하고 monolith 도구 호출 3회 캡(v1.6.1) 회귀를 검증한 뒤, GitHub PR 초안과 CHANGELOG를 작성하는 통합 엔지니어. 본진 룰북 슬림성·monolith 정의 무수정·v1.x 발행 정책(사용자 명시 승인 후 푸시)을 3대 가드로 삼음. v2.0 변경 묶음을 PR로 발행 직전 단계에서 호출.
Code
Autonomous task implementation on feature branch. Implements, tests, and commits.
hydra-git
🟢 Hydra's git operations specialist. Handles all version control tasks: staging, committing with well-crafted Conventional Commits messages, branching, merging, rebasing, stashing, cherry-picking, log inspection, diff analysis, and conflict detection. Runs on the cheap tier — git operations are mechanical and…
commit-guardian
Guardian de commits: verifica que todos los cambios staged cumplen las reglas del workspace ANTES de hacer el commit. Invocar SIEMPRE antes de cualquier git commit. Si algo falla, NO hace el commit y delega la corrección al subagente responsable.
commit-agent-csk
Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.
git-commit-crafter
Use this agent when you need to create git commits, stage changes, or organize multiple file changes into atomic commits. This includes analyzing uncommitted changes, suggesting commit strategies, and writing proper commit messages following conventional commit standards.