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.
git 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/rules/webhook-co/webhook/infra-devops)<a href="https://agentmods.dev/rules/webhook-co/webhook/infra-devops"><img src="https://agentmods.dev/badge/rules/webhook-co/webhook/infra-devops/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/rules/webhook-co/webhook/infra-devops"><img src="https://agentmods.dev/badge/rules/webhook-co/webhook/infra-devops.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.00345 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
infra-devops 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
Infra & DevOps guardrails
- Cloudflare-forward + TypeScript is the settled core (2026-06-10). Default new compute to Workers / Durable Objects. Don't reintroduce rejected alternatives without an ADR.
- Keep the container-delivery seam. Heavy/blocking outbound delivery sits behind an abstraction interface so the compute lane (Workers vs container) can change without engine changes. Never couple the engine directly to a specific delivery backend.
- Datastore choices are deliberate: Neon Postgres via Hyperdrive for metadata/dedup (not D1); Cloudflare R2 for batched payload bodies; Workers KV for hot config cache. Don't swap these casually.
- No destructive infra without review. Anything that deletes/recreates resources, drops data,
rotates production secrets, or changes DNS/routing for
webhook.coorwbhk.myrequires explicit human review. Preferwrangler ... --dry-run/ plan output first. - Ingestion isolation is structural.
wbhk.mystays a separate registrable apex: cookieless, no CORS, path-token routing. Don't route ingestion through app subdomains. - Config as code, secrets out of code. All infra is reproducible from
infra/; secrets come from the secret store /wrangler secret, never committed. No account/zone IDs in the repo. - Observability is not optional. Wire OpenTelemetry traces/metrics for new services.
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 · 25 lines · 0 tokens per session scan A 04fd88126351
infra-devops is a cursor rule published in the GitHub repository webhook-co/webhook (0 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 345 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 cursor rules, from other repositories
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
previews
Cloudflare Worker Previews pipeline - credential-free Preview build then cf previews deploy, cf previews delete, Wrangler-only secrets, Access before arming, agent loop.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.
hatch3r-progressive-delivery
Progressive delivery — canary, blue-green, feature-flag rollout with auto-rollback on SLO burn; staged rollout to prevent CrowdStrike-class incidents.
hatch3r-scalability
CQ6 Scalability Quality measurement rule — stateless-handler ratio, back-pressure pattern adoption, idempotency-key adoption on POST/PUT/PATCH, queue offloading for >1s ops, pool sizing per concurrency profile.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.