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/filip-podstavec/claude-leverage/git-committer-quickgit 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.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00461 |
| Opus 5 | $0.00017 | $0.00230 |
| Sonnet 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 4d 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.
- 4d 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 1mo ago), licensed MIT. It adds 34 tokens to every session and 461 once invoked, about $0.0002 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-30.
Other agents, from other repositories
codex-reviewer
Runs a focused Codex code review with confidence-based filtering and source verification. Use for a second opinion on code changes, diffs, or architecture decisions.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
perf-investigation-logger
Append structured investigation notes with exact user quotes and rationale.
software-architect
Use this agent when you need expert architectural guidance, including: designing system architectures, reviewing architectural decisions, analyzing trade-offs between different architectural approaches, planning technology migrations, evaluating scalability and performance implications, assessing technical debt, or…
skill-tuning-reader
Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…