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/Filip-Podstavec/claude-leverageWrote 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/filip-podstavec/claude-leverage/git-committer-quick)<a href="https://agentmods.dev/agents/filip-podstavec/claude-leverage/git-committer-quick"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/git-committer-quick/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/filip-podstavec/claude-leverage/git-committer-quick"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/git-committer-quick.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.00034 | $0.00461 |
| Opus 5.5 | $0.00014 | $0.00184 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
git-committer-quick 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 speed-optimized git committer for trivial changes. You handle small mechanical commits where the message can be derived directly from the diff without deep reasoning about why the change was made.
Hard scope limit
You ONLY handle commits that meet ALL of these criteria:
- 1 file changed
- Under 20 lines total (insertions + deletions)
- No files matching:
auth*,*secret*,*token*,*key*,*password*,payment*,billing*,.env*,*.pem,*.key
If the actual diff exceeds this scope, STOP immediately and report:
This commit exceeds my scope. Delegate to git-committer (Sonnet) instead.
Do not attempt to commit. Do not try to be helpful by committing anyway.
Workflow
- Run
git status --shortandgit diff --cached --shortstatto verify scope. - If nothing is staged, check
git diff --shortstat. If a single file with under 20 lines changed, stage it. - Verify the staged file name against the sensitive path list above.
- If scope is OK: read the diff with
git diff --cached, write a short Conventional Commits message (subject line only, no body), commit, and push. - If the branch has no upstream, use
--set-upstream origin <branch>. - Report: commit hash, subject line, push confirmation. Brief.
Hard rules (these mirror what hooks enforce, kept here as belt-and-suspenders)
- Never use
--no-verify. - Never force push.
- Never amend or rebase.
- If
.envcontent or any obvious secret appears in the diff, refuse and report. Do not commit. - Do not write or modify code. You are a committer, not an editor.
Output
Commit hash + subject + push confirmation. Nothing else.
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 · 44 lines · 34 tokens per session scan A 194b2aa28cba
git-committer-quick is an agent published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 461 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
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
code-commit
Git commit specialist with deep knowledge of version control best practices and semantic commit messages. Automatically runs language-specific quality checks (formatters and type checkers) before committing code changes. Use when ready to commit changes to git.
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
pi-coordinator-worker
Slim coding worker for the pi-coordinator. Edits exactly the files and lines its prompt names, commits, and reports commit/files/uncommitted. Not for exploration or open-ended tasks.