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/yudefine/nuxt-supabase-starter/cloudflare-workersgit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/yudefine/nuxt-supabase-starter/cloudflare-workers)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/cloudflare-workers"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/cloudflare-workers.svg" alt="Measured on agentmods" 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.08945 |
| Opus 5 | $0.00000 | $0.04473 |
| Sonnet 5 | $0.00000 | $0.01789 |
| Haiku 4.5 | $0.00000 | $0.00894 |
Grade A, and why
cloudflare-workers 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 2d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Workers / NuxtHub Configuration
Fleet 內絕大多數 consumer 走 「Nuxt + Nitro
cloudflare_modulepreset + GitHub Actionscloudflare/wrangler-action@v3deploy」 共通骨幹（Track A — wrangler-action）。少數 consumer 改走 void.cloud（Track B — VoidZero 部署平台，建在 Cloudflare Workers 上；current SDK 以 official Nuxt integration 與 OIDC workflow 為準）。差異維度：(1) NuxtHub 是否該帶 (2) wrangler 檔該長什麼樣 (3) deploy 派別（wrangler-action vs void.cloud）。
Cookbook 範本：
~/offline/clade/vendor/snippets/cloudflare-workers/。與 [[data-layer-d1]] 互補：本 rule 規 架構選擇 + 設定格式 + deploy track；data-layer-d1 規 D1 + Drizzle runtime sharp edges（subquery alias、dev binding fallback、schema patch 等）。 與
/yudefine-deployskill 互補：本 rule 規 跨 fleet 通用 hard rule；skill 規 YuDefine fleet 部署 SOP（含 void.cloud Step 3A 決策樹詳述）。
§ 1 — DB × deploy track NuxtHub gating（hard rule）
NuxtHub (@nuxthub/core) 的唯一實質作用是 wrangler-action deploy track 上的 Cloudflare 原生 binding (D1 / KV / R2 / AI / Vectorize / Durable Objects) 的 runtime 抽象。它不提供 deploy 簡化（fleet 內目前無 consumer 用 nuxthub deploy，以 registry 為準），而且：
- 不用 D1/KV/R2/AI 的 consumer（Supabase / Postgres / 純外部 DB）帶
@nuxthub/core是純冗餘 dep - void.cloud track（即使用 D1）帶
@nuxthub/core也是冗餘 — void 提供自家void/db+void/schema-d1abstraction，與 NuxtHub helper 同層但獨立
MUST（採二維 matrix 判定）
| Deploy track | DB | 規約 |
|---|---|---|
| Track A (wrangler-action) | Cloudflare D1 / KV / R2 / AI | MUST 在 package.json 帶 @nuxthub/core + 在 nuxt.config.ts modules 登記 + 設 hub: { db: 'sqlite', ... } + server code 用 hubDatabase() / hubKV() / hubBlob() |
| Track A (wrangler-action) | Supabase / Postgres / 純外部 DB | MUST NOT 帶 @nuxthub/core |
| Track B (void.cloud) | D1（void 自家 provision） | MUST NOT 帶 @nuxthub/core；自己寫 server/utils/db.ts 包 createDb(env.DB) + server/utils/blob.ts 包 R2 raw binding（範本見 /yudefine-deploy Phase 5） |
| Track B (void.cloud) | 純外部 DB（罕見） | MUST NOT 帶 @nuxthub/core（同上） |
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.
- 2d ago First seen · 427 lines · 0 tokens per session scan A 3768139bec33
cloudflare-workers is a cursor rule published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,945 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-09-03.
Other cursor rules, from other repositories
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
platform-engineer
Cursor rule "platform-engineer" from ulises-jeremias/agent-toolkit, covering platform engineer, responsibility, main skill domains, when invoked and delegate to skills.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.