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.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)<a href="https://agentmods.dev/commands/webhook-co/webhook/commit"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/commit/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"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/commit.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.00495 |
| Opus 5.5 | $0.00000 | $0.00198 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
commit 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
Create a commit that matches this repo's history, with the hooks doing their job.
How to run
- Inspect state in parallel:
git status,git diff(unstaged) andgit diff --staged, andgit log --oneline -15to match the existing message style. - Refuse to stage likely-secret files. Never add
.env/.env.*, credential files, key material (*.pem,*.key,id_rsa,*.p12),*.crt, cloud-credential JSON, or anything carrying tokens or account/zone IDs. If such a file is staged or requested, stop and warn me — don't commit it. (See theno-secretsrule.) - Stage the intended changes and write a Conventional Commits message matching history:
type(scope): subject(e.g.feat(engine):,fix(ci):,chore(deps):). Subject in the imperative, concise; add a wrapped body explaining the why when the change isn't trivial. Pass the message via a heredoc so formatting survives. - Commit. Let husky run. The pre-commit hook runs lint-staged (eslint + prettier), the
no-skipped-testscheck, and typecheck.
If the pre-commit hook fails
Fix the root cause and make a new commit. That's the whole point of the gate.
- Never
git commit --no-verify, never disable or skip the husky hook, never--no-verifyin any form. - Never add
.only/.skip/fdescribe/xit, disable a failing test, or lower a coverage threshold to get green. - Local hooks are a convenience and are bypassable — but bypassing them is forbidden here. CI required checks are the real gate and have no bypass for anyone, including admins.
Notes
- Don't push or open a PR — this command only commits. Use
/commit-push-prfor the full flow. - If the change includes user-facing UI/copy that a human must eyeball, say so: it still needs human verification regardless of a clean commit.
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 · 35 lines · 0 tokens per session scan A 8338bfeff0cd
commit 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 495 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.en
Commit the current changes to Git.
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.
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.