Borrowing it
Nothing to install: this file belongs to webhook-co/webhook. 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/webhook-co/webhook/main/.cursor/commands/commit-push-pr.mdgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/commit-push-pr)<a href="https://agentmods.dev/commands/webhook-co/webhook/commit-push-pr"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/commit-push-pr/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/commands/webhook-co/webhook/commit-push-pr"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/commit-push-pr.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.00000 | $0.00473 |
| Opus 5.5 | $0.00000 | $0.00189 |
| Sonnet 5.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 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
/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.
- 1mo ago 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 18d 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
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.