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-port-allocation)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/dev-port-allocation"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/dev-port-allocation/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-port-allocation"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/dev-port-allocation.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.05013 |
| Opus 5 | $0.00000 | $0.02507 |
| Sonnet 5 | $0.00000 | $0.01003 |
| Haiku 4.5 | $0.00000 | $0.00501 |
Grade A, and why
dev-port-allocation 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 yesterday.
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Port 中央分配
核心命題：consumer 越來越多，dev server port 撞號是 cross-cutting concern — 不集中分配必然撞。本規約把 dev port 變成 clade 標準層治理：registry 集中分配、規約強制宣告、audit 偵測漂移與衝突。
SoT：
registry/consumers.json每個 consumer entry 的dev_portsobject。Audit gate：
scripts/dev-port-audit.ts（DRIFT / MISSING / CONFLICT → exit 1）。Cookbook 範本：
vendor/snippets/dev-port/。Preview 轉發：
/__preview/<port>在 request-time 用previewListenerDecision確認 listener cwd 屬於該 port 的主人。mismatch / unknown MUST 出自我頁， NEVER 把別的 consumer 的 HTML（含 Nuxt welcome）嵌進驗收畫面。
MUST
1. 顯式宣告 port
- MUST consumer
package.json的devscript 必須顯式帶--port <registry.dev_ports.nuxt> - NEVER 裸
nuxt dev（吃 Nuxt default 3000） - NEVER 省略
--portflag - NEVER 寫
pnpm dev -- --port <N>來補 flag：多出來的--會讓 Nuxt 把--port當位置參數丟掉，又落到 default 3000。要覆寫 port 用pnpm dev --port <N>（沒有中間那個--），且 script 本身仍 MUST 帶--port scripts/dev-port-audit.ts對 DRIFT / MISSING / CONFLICT MUST exit 1。NEVER 把它當 diagnostic-only 吞掉 exit code
2. Tunnel port 對齊
- MUST consumer
nuxt.config.ts若使用vite-plugin-cloudflare-tunnel，plugin 的port:必須等於 registrydev_ports.nuxt - 寫法可為 hard-code number 或
Number(process.env.NUXT_DEV_PORT ?? <registry-value>)，audit 兩種都接受
2.5. Dev tunnel zone & token convention（vite-plugin-cloudflare-tunnel）
凡 consumer 用 vite-plugin-cloudflare-tunnel 開 dev tunnel：
-
MUST Hostname 走
<consumer-id>-dev.<maintainer-domain>（org convention；既有對齊：<consumer-i>-dev/<consumer-b>-dev/<consumer-a>-shared-dev/co-purchase-dev） -
NEVER 自由發揮挑其他 zone（如
bigbyteedu.com/ 個人域名）— 即使 DNS / tunnel 建得起來，plugin 仍會因 token-zone account 不匹配 403 crash Nuxt -
MUST
.env.local設三件套：TUNNEL_HOSTNAME=<consumer-id>-dev.<maintainer-domain> TUNNEL_NAME=<consumer-id>-dev CLOUDFLARE_API_KEY=<cfat_*-token>
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.
- yesterday Changed · +1 lines 253fcee15e77
- 5d ago First seen · 209 lines · 0 tokens per session scan A 9f82bb21deba
dev-port-allocation 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 5,013 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
no_default_dev_hub
How to resolve the "No default dev hub found" error in Salesforce DX.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.