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/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/dev-tunnel-convention)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/dev-tunnel-convention"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/dev-tunnel-convention/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/yudefine/nuxt-supabase-starter/dev-tunnel-convention"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/dev-tunnel-convention.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.03101 |
| Opus 5 | $0.00000 | $0.01550 |
| Sonnet 5 | $0.00000 | $0.00620 |
| Haiku 4.5 | $0.00000 | $0.00310 |
Grade A, and why
dev-tunnel-convention scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` 怎麼打都正確 —— curl 不會像瀏覽器那樣先發 stylesheet 請求再發 module 請求，拿不到被污染的那個條目 How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Tunnel Convention（索引）
核心命題：dev tunnel（透過 vite-plugin-cloudflare-tunnel 或手動 cloudflared）是 cross-cutting concern — 跨多個 consumer 共用同一組 org convention（zone / token / hostname）與同一類失敗模式（token-zone account 不匹配、restart loop lockout、cold-load 誤判 hang）。本檔是索引 hub：把已散落在 [[dev-port-allocation]] § 2.5/2.6/2.7 與 vite-tunnel skill cookbook 的四題彙整，每題給一句 convention + 指向權威來源 + 對應 pitfall。
真相層：本檔不重複規約細節。每個 sub-§ 的 MUST/NEVER 與範本以「指向處」為唯一來源（[[dev-port-allocation]] 或 cookbook README）；本檔只做 convention 摘要 + 入口導航，避免兩處 drift。
觸發本檔的 consumer 端閱讀時機：寫 / 改
nuxt.config.ts的viteCloudflareTunnel呼叫、設.env(.local)的 tunnel 三件套、量測 dev-over-tunnel 載入效能、或在多 Cloudflare account 環境跑cloudflared tunnel route dns。
§ 1 — Zone 必在當前 account 內（multi-account misdirection）
Convention：dev tunnel hostname 一律走 <consumer-id>-dev.<maintainer-domain>（org convention）。NEVER 自由挑其他 zone（bigbyteedu.com / 個人域名）。
為什麼：cloudflared tunnel route dns 在多 Cloudflare account 環境下，若 hostname 對應 zone 不在當前 ~/.cloudflared/cert.pem 綁定的 account 內，不會 fail-loud，而是 silently 把整段 hostname 當 subdomain prefix 附加到該 account 第一個 zone（如寫成 <host>.<maintainer-domain>.bigbyteedu.com），外部 DNS 永遠 resolve 不到，但 CLI exit 0。
權威來源：
- vite-tunnel skill cookbook
~/offline/clade/vendor/snippets/vite-tunnel/bin/dev-tunnel-setup.sh（以顯式 account／zone 比對 API 回應與 cloudflared certificate 身分；建立前檢查 tunnel／DNS，route 後回讀 DNS）+ 同目錄 README § 多 Cloudflare account 使用情境 - hostname convention 規約：[[dev-port-allocation]] § 2.5
Pitfall：[[pitfall-cloudflared-multi-account-cname-misdirection]]
§ 2 — Token scope：必用 cfat_*（含 SSL:Edit）
Convention：.env(.local) 的 CLOUDFLARE_API_KEY MUST 是 cfat_* account API token，NEVER 用 cfut_*（Worker token）或 r_*（cloudflared tunnel login 簽發的 cert.pem token）。必備權限三條：Cloudflare Tunnel:Edit（account）+ SSL and Certificates:Edit（zone）+ DNS:Edit（zone）。
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 Changed · +1 lines ef9ef6c61c6a
- 6d ago First seen · 124 lines · 0 tokens per session scan A 0cf20011991b
dev-tunnel-convention 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 3,101 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.
cloudflare-infrastructure
Cloudflare infrastructure patterns and best practices.
cloudflare-workers
Cloudflare Workers specific patterns and requirements.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
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.