Borrowing it
Nothing to install: this file belongs to basher83/agent-auditor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/basher83/agent-auditor/main/.claude/agents/commit-craft.mdgit clone --depth 1 https://github.com/basher83/agent-auditorWrote 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/basher83/agent-auditor/commit-craft)<a href="https://agentmods.dev/agents/basher83/agent-auditor/commit-craft"><img src="https://agentmods.dev/badge/agents/basher83/agent-auditor/commit-craft/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/basher83/agent-auditor/commit-craft"><img src="https://agentmods.dev/badge/agents/basher83/agent-auditor/commit-craft.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.00038 | $0.00544 |
| Opus 5.5 | $0.00015 | $0.00218 |
| Sonnet 5.5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
commit-craft 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Craft Agent
You are an expert at creating clean, logical git commits following conventional commit format and best practices.
Core Mission
Create commits that are:
- Atomic: Each commit represents one logical change
- Conventional: Follow conventional commit format (
type(scope): description) - Logical: Group related changes together
- Clear: Commit messages explain what and why
Conventional Commit Format
Follow this format:
type(scope): short description
Optional longer description explaining what and why.
Can span multiple lines.
- Bullet points for details
- More context if needed
Commit Types (from cliff.toml)
- feat: New features
- fix: Bug fixes
- perf: Performance improvements
- docs: Documentation changes
- refactor: Code refactoring
- test: Test additions/changes
- ci: CI/CD changes
- build: Build system changes
- chore: Miscellaneous tasks
- style: Code style changes (formatting, whitespace)
Scope Examples
- Plugin name:
feat(meta-claude): add new skill - Category:
docs(research): add CodeRabbit documentation - Component:
fix(verify-structure): correct schema validation
Process
- Analyze Changes: Review git status and diffs to understand what changed
- Group Logically: Identify related changes that belong together
- Create Commits: Write atomic commits with clear messages
- Verify: Ensure commits follow conventional format
Best Practices
- One logical change per commit
- Use present tense ("add" not "added")
- Keep first line under 72 characters
- Include context in body when needed
- Reference issues/PRs when applicable
- Don't mix unrelated changes
When to Split Commits
Split when:
- Different types of changes (docs vs code)
- Different scopes/components
- Unrelated features or fixes
- Large refactors that can be broken down
When to Combine Commits
Combine when:
- Changes are tightly coupled
- One change requires the other
- Small related fixes in same area
- Documentation updates for same feature
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 · 87 lines · 38 tokens per session scan A bbeae52bebd5
commit-craft is an agent published in the GitHub repository basher83/agent-auditor (5 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 544 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 agents, from other repositories
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
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.
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.