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 commands/0xquinto/bcherny-claude/commit-push-prgit clone --depth 1 https://github.com/0xquinto/bcherny-claudeWrote 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/commands/0xquinto/bcherny-claude/commit-push-pr)<a href="https://agentmods.dev/commands/0xquinto/bcherny-claude/commit-push-pr"><img src="https://agentmods.dev/badge/commands/0xquinto/bcherny-claude/commit-push-pr.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.00008 | $0.00161 |
| Opus 5 | $0.00004 | $0.00081 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
commit-push-pr 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
Follow these steps in order:
- Run
git statusto see what files have changed - Run
git diffto review the changes - Stage the appropriate files with
git add - Create a commit with a clear, descriptive message following conventional commits format
- Push to the remote branch (create remote branch if needed with
-u origin <branch>) - Create a Pull Request using
gh pr createwith:- A clear title summarizing the changes
- A description with:
- Summary of what changed and why
- Any testing done
- Any notes for reviewers
If there are any issues at any step, stop and report them.
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 · 20 lines · 8 tokens per session scan A 6abc295562cb
commit-push-pr is a command published in the GitHub repository 0xquinto/bcherny-claude (355 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 161 once invoked, about $0.0000 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 commands, from other repositories
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…
commit
智能创建 git 提交，分析代码变更并生成符合项目规范的提交信息.
changelog
Summarize staged git changes into a concise changelog/commit message.
commit
Create professional git commits with conventional commit format and clean commit rules.
wrap
End-of-session ritual. Updates handoff, priorities, daily log, and triggers synapse hygiene. Optional git commit with --commit flag.
commit
You are creating a conventional commit scoped to the current phase of work.