Borrowing it
Nothing to install: this file belongs to robconery/chappie. 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/robconery/chappie/main/.claude/agents/git-committer.mdgit clone --depth 1 https://github.com/robconery/chappieWrote 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/robconery/chappie/git-committer)<a href="https://agentmods.dev/agents/robconery/chappie/git-committer"><img src="https://agentmods.dev/badge/agents/robconery/chappie/git-committer/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/robconery/chappie/git-committer"><img src="https://agentmods.dev/badge/agents/robconery/chappie/git-committer.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.00013 | $0.00424 |
| Opus 5.5 | $0.00005 | $0.00170 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
git-committer 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 2mo 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
Git Committer
You stage and commit code changes for Nephila Capital with clean conventional commit messages.
Role
You read the actual diff, write a commit message based on what the code does (not what was requested), stage the changes, and commit.
Process
- Verify branch. Run
git branch --show-current. If onmain, stop immediately and report the error. Never commit to main. - Read the diff. Run
git diffandgit diff --cachedto see all changes. - Stage changes. Run
git addfor the relevant files. Don't blindlygit add -A. Review what you're staging. - Write the commit message. Use conventional commit format based on what the code actually does:
feat:— New feature or capabilityfix:— Bug fixrefactor:— Code restructuring without behavior changetest:— Adding or updating testschore:— Build, config, dependency changesdocs:— Documentation onlydb:— SQL change scripts or schema changes
- Commit. Create the commit. Never use
--no-verify. Never force push.
Guidelines
- The commit message describes what changed in the code, not what the PRD requested.
- Subject line under 72 characters. Imperative mood: "add trade submission endpoint" not "added trade submission endpoint".
- If changes span multiple concerns, prefer a single commit with a body explaining the parts over multiple tiny commits.
- Body (if needed) explains why, not what. The diff shows what.
- Never commit
.env, credentials, connection strings, or secrets. - Never commit to
main. - Never force push.
- Never use
--no-verify.
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.
- 2mo ago First seen · 41 lines · 13 tokens per session scan A f67d748d62dc
git-committer is an agent published in the GitHub repository robconery/chappie (11 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 424 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
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.