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 rules/webhook-co/webhook/git-workflowgit 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.00438 | $0.00438 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
git-workflow 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
Git workflow (branch hygiene)
We open many short-lived branches in parallel. They drift from main fast, and stale branches
produce avoidable merge conflicts, redundant review of already-merged code, and CI that passed
against an old base. Keep every branch close to main.
Rebase on main — non-negotiable
- Before opening a PR, rebase the branch onto the latest
origin/main:git fetch origin && git rebase origin/main. Resolve conflicts locally; never open a PR from a base more than a few commits behindmain. - Before pushing an update to an open PR (e.g. addressing review), fetch and rebase onto
origin/mainfirst, so the PR is reviewed and CI-checked against the current base. - Keep rebasing frequently while a branch is open — at minimum whenever another PR merges to
main. Don't let a branch sit behind. If several review branches were cut from the same oldermain, rebase each one as the earlier ones land.
How
git fetch origin && git rebase origin/main(interactive rebase flags like-iare unavailable in the agent harness — do a plain rebase).- After a rebase that changes already-pushed history, force-with-lease:
git push --force-with-lease. Never plain--force. - Re-run the gate after every rebase: typecheck, the affected test suites, and lint must pass on the rebased tree before pushing. A clean pre-rebase run does not transfer.
Never weaken the gate
- Never
git commit --no-verify/git push --no-verify. CI required checks are the real gate. - Conventional Commits. Branch off
main; do not commit directly tomain. - Don't self-merge — PRs are the human's to merge unless explicitly told otherwise.
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 · 38 lines · 438 tokens per session scan A 309a068c5d94
git-workflow is a cursor rule published in the GitHub repository webhook-co/webhook (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 438 tokens to every session, about $0.0022 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-31.
Other cursor rules, from other repositories
docs
All documentation files use MDX format with a specific structure.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
turborepo
Turbo query graph primitives and signed remote-cache key provisioning.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.
boundaries
Package dependency boundaries - tag map and enforced invariants.
react
React 19 SPA invariants - client-only, no fetch in useEffect, Compiler memo policy.