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/workers-cache)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/workers-cache"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/workers-cache/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/workers-cache"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/workers-cache.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.00474 | $0.00474 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
workers-cache 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 23d 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
Workers Cache Rules
Tiered edge cache in front of Worker fetch() entrypoints (eyeball, binding fetch(), ctx.exports.fetch()) - not caches.default. Control with Cache-Control / Cache-Tag; purge with ctx.cache.purge() (docs). Out of scope: webhook-*, front-app. Depth: skill workers-best-practices.
- Unsafe methods: never cache; purge the
Cache-Tagon writes. Probes and real-time responses:no-store. Public read-heavy GET:public, max-age=N, stale-while-revalidate=M+Cache-Tag. - Auth'd shared GET: uncached gateway → strip
Authorization→ cached innerfetch. Per-user:ctx.props+ stripAuthorization. worker-api'scloudflare.config.tsgives staging, production, and the PreviewEDGE_CACHE-cache: { enabled: true }withexports: { default: exports.worker({ cache: { enabled: false } }) }. Development (andTEST, which spreads it) setscache: { enabled: false }andexports: {}: the Vite plugin 2.0 beta'svite deventry emitsexport const <key> = …for everyexportskey, soexports.defaultbecomesexport const defaultand workerd refuses to start ("Unexpected token 'default'"); builds and the Vitest pool are unaffected. PutEDGE_CACHEback on development once a plugin release startscf devwith it.- Never enable cache on the gateway and then return
no-store: it still pays the tier lookup. - Worker-to-Worker defaults to RPC, which is not cacheable. Use binding
fetch()only for hot read paths where a HIT skips callee CPU. Debug withCf-Cache-Status.
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.
- 23d ago Changed · -1 lines · +108 tokens per session 758aaef82bc6
- 27d ago Changed · +1 tokens per session 01b78977df66
- 1mo ago First seen · 17 lines · 365 tokens per session scan A 768ccff1227a
workers-cache is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It adds 474 tokens to every session, about $0.0019 per session on Opus 5.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-30.
Other cursor rules, from other repositories
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
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.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.