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-featuregit 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-feature)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/specformula-feature"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-feature/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-feature"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-feature.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.00023 | $0.01210 |
| Opus 5 | $0.00012 | $0.00605 |
| Sonnet 5 | $0.00005 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
specformula-feature 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecFormula Feature 撰寫指南
SpecFormula 的 .feature 檔案使用 Gherkin DSL 搭配 ISA 指令與符號系統,以宣告式語法定義 BDD 測試。每個指令的 Gherkin 語法由 isa.yml 的 instructions[].format 正則表達式定義,撰寫前請先查看專案的 isa.yml 確認實際格式。
撰寫 SOP
新增 Feature
規劃新功能的完整測試檔案,依照 Step 1 → Step 2 → Step 3 流程撰寫所有 Scenario。
新增 Scenario
在現有 .feature 檔案中新增測試場景,依照 Step 1 → Step 2 → Step 3 流程撰寫。
新增 Step
在現有 Scenario 中新增步驟,根據步驟類型(Given / When / Then)參考對應的決策樹。
Step 1:前置條件(Given)
根據測試場景需要的初始狀態,判斷需要哪些前置條件:
- 測試涉及時間相關欄位(如
createdAt、updatedAt)?→ TimeControl(讀取time-control.md) - 測試需要模擬時間推移?→ 多次 TimeControl(讀取
time-control.md) - 需要準備資料?→ EntitySetup(讀取
entity-setup.md) - 需要前置 API 流程?→ ApiCall(讀取
api-call.md) - 需要自訂步驟?→ Custom(讀取
custom.md)
Background:
# 1. 固定時間
Given 現在時間為 "2026-01-27T10:00:00"
# 2. 直接插入資料庫
Given 準備一個使用者, with table:
| >Alice.id | name | email | passwordHash | status |
| <userId | Alice | [email protected] | password123 | ACTIVE |
Step 2:事件(When)
- 執行 HTTP API 請求?→ ApiCall(讀取
api-call.md) - 需要自訂步驟?→ Custom(讀取
custom.md)
# 前置 API(取得 Token)
When (No Actor) 使用者登入, call table:
| >AliceToken | email | password |
| <token | [email protected] | password123 |
# 被測試的 API
When (UID="$Alice.id") 新增待辦事項, call table:
| >todo1.id | title | description |
| <todoId | 買牛奶 | 去全聯買 |
Step 3:後置條件驗證(Then)
驗證事件執行後的結果:
- 驗證 API 狀態碼與回應內容?→ ResponseValidate(讀取
response-validate.md) - 需要存在特定資料?→ EntityValidate(讀取
entity-validate.md) - 需要不存在特定資料?→ EntityNonExistenceValidate(讀取
entity-non-existence-validate.md) - 需要自訂步驟?→ Custom(讀取
custom.md)
# 1. 回應驗證
Then 新增待辦事項(201)回應, with table:
| todoId | userId | title | completed |
| $todo1.id | $Alice.id | 買牛奶 | false |
# 2. 資料庫狀態驗證
And 應該存在一個待辦事項, with table:
| todoId | userId | title | completed | createdAt |
| $todo1.id | $Alice.id | 買牛奶 | false | &sameTime("2026-01-27T10:00:00") |
What ships with it
11 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.
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 · -6 lines 7aaba331e38b
- yesterday First seen · 102 lines · 23 tokens per session scan A 9204f26033bc
specformula-feature is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,210 once invoked, about $0.0001 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
nw-fp-hexagonal-architecture
Hexagonal architecture patterns with pure core and side-effect shell for functional codebases.
nw-bdd-methodology
BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
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"…
shaft-api-testing
Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.
api-contract-testing
Pact consumer test — JavaScript (checkout-service consuming payments-api).