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 spec-by-examplegit 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/spec-by-example)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/spec-by-example"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/spec-by-example/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/spec-by-example"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/spec-by-example.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.00076 | $0.00917 |
| Opus 5 | $0.00038 | $0.00458 |
| Sonnet 5 | $0.00015 | $0.00183 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
spec-by-example 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.
What it actually says
Spec By Example
spec-by-example 產出 PM 可 review 的總驗收 Gherkin。這一層仍屬於 plan：它描述本次迭代希望達成的業務旅程，不是目前系統的 interface truth。
SOP
Phase 1 -- 對齊 plan spec 與輸出位置
- READ 讀取使用者需求、呼叫者要求、目標 plan package 的
spec.md、既有features/acceptance/內容，以及必要的specs/truth/**高層現況。 - READ 讀取
rules/輸出位置與acceptance切檔判準.md，確認 acceptance feature files 必須輸出到當前 plan package。 - WRITE 若
specs/plans/NNN-<slug>/features/acceptance/尚不存在，建立該目錄。
Phase 2 -- 收斂驗收旅程與需求缺口
- READ 讀取
rules/gherkin-驗收句型與結構判準.md、templates/acceptance.feature、templates/acceptance.example.feature、templates/電商範例/features/acceptance/訂單成立與付款超時.feature、templates/電商範例/features/acceptance/庫存預留與超賣防護.feature、templates/電商範例/features/acceptance/折扣疊加與互斥.feature、templates/電商範例/features/acceptance/滿額贈品與條件取消.feature與templates/電商範例/features/acceptance/運費分區與免運判定.feature，確認 acceptance Gherkin 的顆粒度、句型、Rule / Example 邊界與完成樣貌。 - THINK 依
spec.md的 User Stories、Acceptance Criteria、邊界情況與全域需求，收斂少量但關鍵的 Journey 型驗收流程。 - READ 若需求存在會改變 Journey、規則歸屬、驗收結果或切檔的高影響缺口，讀取
rules/缺口標記與Clarify升級判準.md。 - DELEGATE 若仍有高影響缺口，呼叫
/clarify；未收斂前停止，不自行假設答案。
Phase 3 -- 產出 acceptance Gherkin
- WRITE 在目標 plan package 的
features/acceptance/下建立或更新 feature files；Gherkin 維持業務語言，不拆前端 / 後端，也不產出dsl.md。 - WRITE 將高影響未定事項直接標在對應 feature 的規則或步驟旁，格式固定為
# [need clarification] ...。 - READ 回頭檢查每份 feature 是否與
spec.md一致、可被 PM 直接閱讀，且不與已知 truth 明顯衝突；若不符合，立即修正或升級 clarify。
Phase 4 -- 交付後續 handoff
- WRITE 向使用者回報寫入的 acceptance feature files、已澄清決策、剩餘
# [need clarification]，以及是否可進入/system-analysis或/dsl-refine。
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- rules/gherkin-驗收句型與結構判準.md 7.5 KB
- rules/缺口標記與Clarify升級判準.md 5.5 KB
- rules/輸出位置與acceptance切檔判準.md 1.5 KB
- templates/acceptance.example.feature 1.3 KB
- templates/acceptance.feature 1.1 KB
- templates/電商範例/features/acceptance/庫存預留與超賣防護.feature 1.9 KB
- templates/電商範例/features/acceptance/折扣疊加與互斥.feature 3.1 KB
- templates/電商範例/features/acceptance/滿額贈品與條件取消.feature 1.8 KB
- templates/電商範例/features/acceptance/訂單成立與付款超時.feature 3.5 KB
- templates/電商範例/features/acceptance/運費分區與免運判定.feature 2.3 KB
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 14f8c7a7f1e5
- 2d ago First seen · 43 lines · 76 tokens per session scan A a821dd11d5dd
spec-by-example is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 917 once invoked, about $0.0004 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
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"…
python
Python development with ruff, mypy, pytest - TDD and type safety.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
etl-stabilization
Phase-based orchestrator for fixing SnowConvert ETL conversion gaps in ETL-to-Snowflake migrations (SSIS, Informatica, and other platforms). Analyzes units holistically, creates a ROADMAP with test strategies, and executes fixes through phased TDD with cross-phase learning. Use when user says "fix ETL unit", "fix SSIS…
bug-fix
Regression-first TDD bug fix workflow with real tests. Use when: fixing bugs, resolving regressions, addressing runtime errors, debugging failures, or when the user reports something broken. Triggers on words like: bug, broken, error, crash, regression, not working, fix.