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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/hono-gateway)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/hono-gateway"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/hono-gateway/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/louisbrulenaudet/monorepo-template/hono-gateway"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/hono-gateway.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.01802 |
| Opus 5 | $0.00000 | $0.00901 |
| Sonnet 5 | $0.00000 | $0.00360 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
hono-gateway 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hono Gateway (Workers) Rules
worker-api and sibling worker-* / webhook-* apps use Hono on Cloudflare Workers. For deep patterns load the hono and workers-best-practices skills.
Request lifecycle
flowchart TD
Client["Client / front-app"] --> ReqId["request-id"]
ReqId --> Sec["secure headers"]
Sec --> CORS["CORS (/api/*)"]
CORS --> CSRF["CSRF (unsafe methods)"]
CSRF --> Timing["timing (dev only)"]
Timing --> Timeout["timeout"]
Timeout --> Body["body limit"]
Body --> Validation["zValidator at boundary"]
Validation --> Handler["thin route handler"]
Handler --> Binding["service binding (optional)"]
Handler --> Response["c.json()"]
Middleware order (src/index.ts)
Register in this order. The onion model runs "before" logic top-down and "after" logic (response mutation) bottom-up.
Root app (every route):
requestId()(hono/request-id) - first, so every error log and response can reference it. Setsc.get("requestId")and echoes theX-Request-Idresponse header. AddRequestIdVariablesto the Hono generic'sVariablessoc.get("requestId")is typed.secureHeaders()(hono/secure-headers) - HSTS,nosniff,no-referrer, COOP/CORP on by default (andX-Powered-Byremoved). Add a locked-downcontentSecurityPolicy(default-src 'none'; frame-ancestors 'none') - harmless for JSON, hardening if a response is ever rendered. SetpermissionsPolicyto deny camera/mic/geolocation/payment. CORPsame-originis fine for CORS-modefetchfromfront-app; do not disable it to fix SPA reads.cors()on/api/*- preflightOPTIONSmust clear before auth/routes. Read the allowlist fromc.env.CORS_ORIGINSper request (env is not available at module scope on Workers). PutX-Request-IdinexposeHeadersso browsers can read the id. Empty allowlist is permissive (*) indevonly; any otherENVIRONMENT(includingstaging/productionand typos) must set origins or/api/*returns 503.- Origin / CSRF gate on
/api/*- unsafe methods only (anyContent-Type, includingapplication/json); must not block CORS preflight. Allows when Origin is on the allowlist orSec-Fetch-Siteissame-origin/same-site. Hono built-incsrf()only covers form content-types - do not rely on it alone for this JSON SPA gateway.
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.
- 11d ago First seen · 91 lines · 0 tokens per session scan A 708f7890a854
hono-gateway is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,802 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-30.
Other cursor rules, from other repositories
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
knative-istio-typesense-gpu-cursorrules-prompt-fil
Cursor rules for Knative development with Istio, Typesense, and GPU integration.
netlify-official-cursorrules-prompt-file
Cursor rules for Netlify development with official integration.
serverless
Serverless architecture patterns and Lambda/function best practices.