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 skills add YuDefine/nuxt-supabase-starter --skill specformula-entity-specgit 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/skills/yudefine/nuxt-supabase-starter/specformula-entity-spec)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/specformula-entity-spec"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-entity-spec/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/skills/yudefine/nuxt-supabase-starter/specformula-entity-spec"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-entity-spec.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.00033 | $0.00561 |
| Opus 5 | $0.00016 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
specformula-entity-spec 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 today.
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.
What it actually says
SpecFormula Entity Spec 撰寫指南
Entity Spec 定義業務實體與資料表的對應關係，是 SpecFormula「規格三巨頭」之一。包含兩個部分：
entity_to_table_mapping.yml：實體名稱 → 資料表名稱*.sql（DDL）：資料表結構定義
SpecFormula 規範
1. 檔案存放位置必須參考 isa.yml 配置檔
Entity Spec 的存放路徑由 isa.yml 的 config.data.source[].resource_path 決定：
# isa.yml
config:
data:
source:
- name: default
resource_path: specs/data # ← 框架讀取路徑
project_path: my-project/src/test/resources/specs/data # ← Lint 報錯路徑
db_type: postgresql # ← DDL 語法依據
對應的檔案結構：
src/test/resources/specs/data/ # ← 與 resource_path 一致
├── entity_to_table_mapping.yml
├── schema.sql # 可拆分為多個 .sql 檔案
├── users.sql
└── todos.sql
2. DDL 格式依 db_type 決定
DDL 語法須符合 isa.yml 中該 Data Source 設定的 db_type 對應的合法 SQL 語法（如 postgresql、mysql、embedded、mssql）。
3. Entity 命名使用業務語言
entity_to_table_mapping.yml 定義此 Data Source 下所有業務實體與資料表的對應關係：
# ✅ 推薦：業務語言
entity_to_table_mapping:
- 會員: members
- 訂單: orders
- 商品: products
# ❌ 避免：技術名稱
entity_to_table_mapping:
- member_entity: members
- tbl_order: orders
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.
- today Changed · -7 lines 42bcca78f7a7
- yesterday First seen · 69 lines · 33 tokens per session scan A 831f552c35a6
specformula-entity-spec is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 561 once invoked, about $0.0002 per session on Opus 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-10.
Other skills, from other repositories
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
product-feature-tech-implement
A development workflow that coordinates separate developer, reviewer, and tester roles to implement a feature design and verify it. TDD, or test-driven development, means using tests as part of guiding the implementation.
prd-v07-implementation-loop
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…
prd-v07-test-planning
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases"…
azure-cosmos-db-py
Build production-grade Azure Cosmos DB NoSQL services following clean code, security best practices, and TDD principles.