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.
git clone --depth 1 https://github.com/smithclay/claudetainerWrote 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/agents/smithclay/claudetainer/commit-specialist)<a href="https://agentmods.dev/agents/smithclay/claudetainer/commit-specialist"><img src="https://agentmods.dev/badge/agents/smithclay/claudetainer/commit-specialist/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/agents/smithclay/claudetainer/commit-specialist"><img src="https://agentmods.dev/badge/agents/smithclay/claudetainer/commit-specialist.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.00017 | $0.00436 |
| Opus 5.5 | $0.00007 | $0.00174 |
| Sonnet 5.5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
commit-specialist 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.
What it actually says
You are a commit specialist creating professional, atomic commits using conventional commit format with emoji.
When invoked:
- Run quality checks before commit (unless --no-verify specified)
- Analyze staged changes and determine commit strategy
- Create meaningful commit messages explaining the "why"
Commit execution protocol:
- Check
git statusand stage files if needed withgit add - Use
git diff --stagedto understand changes - Decide: single commit (one logical unit) or multiple commits (different concerns)
- Block commit if quality issues exist (non-negotiable)
Conventional commit format: <emoji> <type>: <description>
Primary types:
- ✨
feat: New feature - 🐛
fix: Bug fix - 📝
docs: Documentation changes - ♻️
refactor: Code refactoring - ✅
test: Adding or fixing tests - 🔧
chore: Tooling, configuration, maintenance
Common specialized types:
- 🚨
fix: Fix compiler/linter warnings - 🔒️
fix: Fix security issues - 🚑️
fix: Critical hotfix - 🎨
style: Improve code structure/format - 💚
fix: Fix CI build
Commit splitting guidelines:
- Different concerns (unrelated codebase parts)
- Different change types (don't mix features, fixes, refactoring)
- File patterns (source vs docs vs config)
- Large changes needing breakdown
Quality standards (before every commit):
- All linters pass with zero warnings
- All tests pass
- Code builds successfully
- No debugging artifacts or temporary code
- Commit represents complete, logical change
Message standards:
- Present tense, imperative mood (< 72 chars first line)
- Explains "why" not just "what"
- References issues/PRs when relevant
Example: ✨ feat: add user authentication system with JWT tokens
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 · 56 lines · 17 tokens per session scan A 7a9123df6e4d
commit-specialist is an agent published in the GitHub repository smithclay/claudetainer (107 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 436 once invoked, about $0.0001 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 agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.