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/service-bindings)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/service-bindings"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/service-bindings/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/service-bindings"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/service-bindings.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.00640 | $0.00640 |
| Opus 5.5 | $0.00256 | $0.00256 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
service-bindings 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 16d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Bindings (Worker-to-Worker RPC)
Caller
- Bind by Worker-name string in the caller's
env:FOO: bindings.worker({ worker: "worker-foo-production" }), the name taken from theDeploymenttable so each mode binds the callee's matching Worker.exportNameselects a namedWorkerEntrypointexport (default: the default export) and is required when binding a named class. - A string reference types the binding as a plain
Fetcher, without RPC method types. The cf docs' typed form passes the callee'sdefineWorkerconfig, which imports another app'scloudflare.config.tsand failspnpm boundaries(boundaries.mdc). Typed cross-Worker RPC is deferred to the firstworker-*; decide it in that change. Never augmentEnvby hand to type a binding. - Call
env.BINDING.method()from a route handler or service module, andawaitevery call: RPC client methods are always async. Neverenv.BINDING.fetch()when RPC methods are the goal; the exception is a cacheable hot read path (workers-cache.mdc). - Payload schemas live in
@repo/dtos-common/rpc(contracts.mdc). - Cloudflare propagates no custom id across a binding: pass
requestIdas an explicit RPC argument (or queue message field) and log it the same way; traces nest on their own.
Callee
- Extend
WorkerEntrypointfromcloudflare:workersand add public methods - those are what callers invoke. RPC methods cannot live on a plainexport default { fetch }handler. - Default-export the entrypoint class, or export a named class and set
exportNameon the caller. - Bindings are
this.env(a class property ofWorkerEntrypoint:this.env.GREETING,this.env.D1); RPC methods take only their own arguments, norequest/envparameters.
After a binding change
- Callee: exported
WorkerEntrypointclass with public RPC methods. - Caller:
bindings.worker()incloudflare.config.ts, named per mode. - Shared payload schemas in
dtos-common/rpcif needed. pnpm types, thenpnpm check-types.- The first
worker-*binding also adds thecreateTestHarnessNode suite (checklist inpackages/vitest-config/AGENTS.md), keeping the pool suites.
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.
- 16d ago First seen · 30 lines · 640 tokens per session scan A aeb5e2ab0f8a
service-bindings is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It adds 640 tokens to every session, about $0.0026 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-09-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.