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/webhook-co/webhook/commit-push-prgit clone --depth 1 https://github.com/webhook-co/webhookWhat 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.00000 | $0.00473 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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 yesterday.
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
/commit-push-pr
Commit the current work, push the feature branch, and open a pull request with a summary and a
test-plan checklist. Uses the GitHub CLI (gh).
How to run
- Commit following
/commitexactly — match Conventional Commits style, refuse likely-secret files (.env, credentials, keys, account/zone IDs), and let husky run. If the pre-commit hook fails, fix the root cause and commit again. - Branch. If I'm on
main/master, create a feature branch first (e.g.feat/<short-slug>); never commit feature work straight onto the default branch. - Push the feature branch with upstream tracking (
git push -u origin HEAD). Let the pre-push hook run its affected tests. - Open the PR with
gh pr create, passing the body via a heredoc:- Summary — what changed and why (1–3 bullets).
- Test plan — a checklist of how it was/should be verified, including any surfaces touched (CLI / API / web / MCP) and parity follow-ups.
- Human verification — an explicit checklist item for anything needing human UI/UX/copy review.
- Return the PR URL.
Hard rules (non-negotiable)
- Never
git commit --no-verifyorgit push --no-verify; never skip or disable husky hooks. If a hook fails, fix the root cause and make a new commit — don't force a green. - Never add
.only/.skip/disabled tests or lower coverage to pass. The local hooks are a convenience; CI required checks are the real gate and have no bypass for anyone, including admins. - Never force-push to
main/master. Don't push secrets or files with account/zone IDs. - Human-UI-testing hard stop. If the change includes UI/visual/copy that a human must verify, say so plainly in the PR and do not treat the PR as done or mergeable until a human has checked it.
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.
- yesterday First seen · 31 lines · 0 tokens per session scan A e1f1f2d73890
commit-push-pr is a command published in the GitHub repository webhook-co/webhook (0 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 473 tokens. 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 commands, from other repositories
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo
You are an SEO expert agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. Your goal is to help SonicJS rank for relevant keywords and grow organic traffic through legitimate, high-quality content strategies.
hyperliquid-risk
Mission-critical real-time risk monitoring system with automated alerts, circuit breakers, and emergency shutdown for live Hyperliquid trading by ae.ltd.
migrate
Apply pending D1 migrations to local (default) or remote.
init
Scaffold the project files I like — CLAUDE.md and the /docs skeleton.
design
Interview the solution — architecture, schema, platform. Owns ARCHITECTURE.md + SPEC.md.