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 gherkin-and-dslgit 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/gherkin-and-dsl)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/gherkin-and-dsl"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/gherkin-and-dsl/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/gherkin-and-dsl"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/gherkin-and-dsl.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.00078 | $0.01561 |
| Opus 5 | $0.00039 | $0.00781 |
| Sonnet 5 | $0.00016 | $0.00312 |
| Haiku 4.5 | $0.00008 | $0.00156 |
Grade A, and why
gherkin-and-dsl 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gherkin And DSL
把 Gherkin 與 DSL 收斂成兩件事同時成立:
- PM / 需求方讀得懂 Gherkin
- AI / 測試作者可以直接把 Gherkin + DSL 落地成 step definitions 與測試程式碼
Quick Start
- 先讀目標 feature files、同模組
dsl.md、相關介面根共用dsl.md、上游 testplan / spec。 - 先判斷本輪是「建立」、「檢查」還是「重構」。
- 結構與詞彙一起改,不要只改 Gherkin 不改 DSL。
- 任一 Gherkin 句型若找不到 DSL 對應,先補 DSL,再回填 feature。
- 最終結果必須同時滿足「業務可讀」與「可直接寫測試」。
SOP
Phase 1 -- 收斂輸入與輸出範圍
- READ 讀取使用者需求、目標 feature files、同模組
dsl.md、與目標句型相關的介面根共用dsl.md、上游 testplan / spec,確認本輪介面與處理範圍。 - THINK 判斷本輪是新建、覆蓋驗證、句型收斂、結構重組或嚴格度補強,並盤點要修改的 feature 與 DSL 檔案。
- WRITE 回報修改範圍與會影響切檔或句型邊界的高影響歧義;若有歧義,先停下確認。
Phase 2 -- 盤點測試案例與覆蓋缺口
- READ 讀取 STANDARDS.md 中的「覆蓋與嚴格度標準」與「Gherkin 句型標準」。
- THINK 逐一比對每個 test case 的 Arrange / Act / 預期輸出 / 必須維持不變 / 本案例不驗證,判斷目前的 Gherkin 與 DSL 是否已完整覆蓋;若只是有步驟但語意被稀釋,也算缺口。
- WRITE 列出缺口:缺少句型、句型過胖、DataTable / Background / Rule 邊界錯置、Then 嚴格度不足、或 Gherkin 有技術語句外露。
Phase 3 -- 收斂 Gherkin 句型
- READ 讀取 STANDARDS.md 中的「Gherkin 語言邊界與句型收斂」與「參數 / DataTable 格式」。
- THINK 收斂
Given/When/Then的共用句型:語意相同必須共用;句子過胖就拆成更核心、可重用的步驟;只有多列資料或多欄位摘要時才優先用 DataTable。 - WRITE 修改 Gherkin:補 Given / When / Then、補業務相關預設值註解、調整 DataTable、移除不再需要的搬運期註解與技術細節。
Phase 4 -- 收斂 DSL 詞彙表
- READ 讀取 STANDARDS.md 中的「DSL 必備欄位」、「後端實作語意」與「前端實作語意」。
- READ 若需要建立、移動 DSL row,或判斷句型應由模組或介面根承接,按需讀取
rules/介面功能模組與DSL唯一歸屬判準.md,確認完整契約與唯一歸屬判準。 - THINK 對每個 Gherkin 句型判斷既有 row、DataTable 欄位、預設參數與實作語意是否足夠,並依已載入判準決定唯一權威位置。
- WRITE 在唯一權威 DSL 檔建立或更新 row,確保句型、參數、DataTable 欄位、預設值與實作語意可直接支援 step definition。
Phase 5 -- 做結構優化
- READ 讀取 STANDARDS.md 中的「Feature / Rule / Example」與「Background / Scenario Outline / DataTable 決策」。
- THINK 依功能面向切分 feature files,判斷是否要抽
Rule、Background、Scenario Outline;Rule必須原子化,Example應描述資料情境而不是重複規則句。 - WRITE 重構 feature files:拆檔、抽 Rule、抽 Background、必要時引入 Scenario Outline,並移除被淘汰的單一總表檔。
What ships with it
13 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.
- examples.md 1.4 KB
- examples/ecommerce/features/backend/dsl.md 2.5 KB
- examples/ecommerce/features/backend/折扣/dsl.md 859 B
- examples/ecommerce/features/backend/折扣/折扣碼套用與拒絕.feature 2.1 KB
- examples/ecommerce/features/backend/訂單/dsl.md 1.1 KB
- examples/ecommerce/features/backend/訂單/訂單重算與免運判定.feature 2.0 KB
- examples/ecommerce/features/frontend/dsl.md 348 B
- examples/ecommerce/features/frontend/結帳/dsl.md 2.8 KB
- examples/ecommerce/features/frontend/結帳/結帳頁折扣碼輸入.feature 1.4 KB
- examples/ecommerce/features/frontend/結帳/訂單摘要與免運顯示.feature 1.4 KB
- rules/介面功能模組與DSL唯一歸屬判準.md 5.2 KB
- scripts/audit_feature_dsl_topology.py 10 KB runs code
- STANDARDS.md 6.9 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.
- today Changed · +1 lines 479a5b2a0eb7
- yesterday First seen · 74 lines · 78 tokens per session scan A 52cc43ecbef6
gherkin-and-dsl is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,561 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
Vibe Coding Mastery
The complete operating system for building software with AI. From first prompt to production deployment — prompting frameworks, architecture patterns, testing strategies, debugging playbooks, and production graduation checklists. Works with Claude Code, Cursor, Windsurf, Copilot, and any AI coding tool.
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"…
Learn what defines effective BDD scenarios
Interactive guidance on writing complete, effective BDD scenarios for story-flow.
principles
Metric literacy for what this plugin reports: what cyclomatic complexity, cognitive complexity, Halstead difficulty, lines per file, duplication, coverage, CRAP, and type debt mean, and what none of them can tell you. Four reference files carry the definitions and what each collector computes, each bundled reference…
pair-programming
Skill "pair-programming" from DNYoussef/context-cascade, covering kanitsal cerceve (evidential frame activation), pair programming, kanitsal cerceve (evidential frame activation), when to use this skill and when not to use this skill.