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/fixtures-reference)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/fixtures-reference"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/fixtures-reference/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/fixtures-reference"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/fixtures-reference.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.01682 |
| Opus 5 | $0.00000 | $0.00841 |
| Sonnet 5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
fixtures-reference 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixtures Reference（hard rule）
凡 consumer 含 ## 人工檢查 items 引用具體業務 sample（NFC UID / staff email / business key / entity ID）時，consumer MUST 維護 docs/FIXTURES.md（或 docs/fixtures.md lowercase fallback）作為「測試身分 / 樣本 UID / business key」速查表。
本規則是 manual-review.md「Pre-Review Data Readiness」與「[review:ui] 純功能驗證 step actionability」hard rule 的配套契約 — propose 寫作者在 manual-review item inline 引用 sample 時 MUST 從 docs/FIXTURES.md 抓 stable identifier，避免「某張」「某筆」「找一張」這種模糊指代。
MUST
- MUST 維護
docs/FIXTURES.md在 consumer root（或docs/fixtures.mdlowercase fallback） - MUST 至少含「測試身分」section（標題如
## Test Identities或## 測試身分），列出 dev / staging 環境下 review 階段會用到的：- NFC / 員工卡 UID 與對應的 holder name + role
- Staff email + role + organization
- Business key samples（work_report id / loan id / equipment id 等）對應的 status / fixture 預期狀態
- MUST propose / ingest 階段在寫
[review:ui]/[verify:ui]item 前先 Readdocs/FIXTURES.md抓 sample identifier - MUST 任何 sample 在 manual-review item inline 引用時，MUST 在
supabase/seed.sql（或專案等價 seed file，permanual-review.md「Pre-Review Data Readiness」§必填三件事 §3）持久化 - MUST
docs/FIXTURES.md列出的 sample 與 seed file 的 INSERT row 一字不差（key field、identifier、stable PK）
NEVER
- NEVER 在 manual-review item inline sample 但 seed 沒對應 row（review 階段會撞 fixture miss）
- NEVER 用 dev DB ad-hoc INSERT 的 sample 作 inline 引用（reset DB 就消失，下個接手者重踩坑）
- NEVER 寫「請使用測試員工 X」要求 user 自找
- NEVER 在
docs/FIXTURES.md寫 production 真實員工 / 真實客戶資料（test fixtures 限於合成 / anonymized 樣本） - NEVER 為了 review 方便動 production 資料庫（fixture 屬 codebase 層，不該污染 production）
Schema（per-consumer 自治）
Clade 中央倉 不規定 docs/FIXTURES.md 內容 schema — per-consumer 業務差異大（kiosk UID 結構、staff role 命名、business key 命名規約都不同）。Clade 只規定該檔 必須 存在、必須含「測試身分」section、必須與 seed cross-link。
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 32c88ff04b15
- 5d ago First seen · 103 lines · 0 tokens per session scan A b3aa0b9aa8c1
fixtures-reference 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 1,682 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
coverage-thresholds
Coverage threshold configuration patterns.
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.