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 wahidyankf/ose-public --skill plan-writing-gherkin-criteriagit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/plan-writing-gherkin-criteria)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/plan-writing-gherkin-criteria"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-writing-gherkin-criteria/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/wahidyankf/ose-public/plan-writing-gherkin-criteria"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-writing-gherkin-criteria.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.00052 | $0.01013 |
| Opus 5.5 | $0.00021 | $0.00405 |
| Sonnet 5.5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
plan-writing-gherkin-criteria 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 2d ago.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gherkin Acceptance Criteria Skill
Purpose
This Skill provides comprehensive guidance for writing Gherkin acceptance criteria using Given-When-Then syntax to create clear, testable specifications for features and user stories.
When to use this Skill: writing acceptance criteria for user stories, defining testable requirements in plans, specifying expected behaviour for features, and documenting edge cases and error handling.
Core Concepts
What is Gherkin?
Gherkin is a structured language for writing acceptance criteria using Given-When-Then syntax. It enables:
- Clear communication: Non-technical stakeholders understand requirements
- Testable specifications: Scenarios map directly to automated tests
- Complete coverage: All scenarios and edge cases documented
- Unambiguous expectations: No room for interpretation
Given-When-Then Structure
Anatomy of a scenario:
Scenario: [Brief description of scenario]
Given [Initial context/preconditions]
When [Action or event occurs]
Then [Expected outcome/postconditions]
Breakdown:
- Given: Sets up the context (initial state, preconditions, setup)
- When: Describes the action or event (user action, system event, trigger)
- Then: Specifies expected outcome (assertions, verification, results)
Journey Coherence
See Journey Coherence for the full rule text, conforming/non-conforming examples, and the canonical convention link.
Basic Scenario Patterns
See Basic Scenario Patterns for three worked patterns: simple success path, error handling, and boundary conditions.
Advanced Gherkin Features
See Advanced Gherkin Features for Background blocks, Scenario Outline with Examples tables, and Data Tables.
Common Domain Patterns
See Domain Patterns — Auth and CRUD and Domain Patterns — Form Validation and API Responses for worked full-feature examples across authentication, CRUD, form validation, and API responses.
What ships with it
12 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.
- README.md 470 B
- reference/advanced-gherkin-features.md 2.2 KB
- reference/basic-scenario-patterns.md 1.4 KB
- reference/common-mistakes.md 2.4 KB
- reference/domain-patterns-auth-and-crud.md 1.9 KB
- reference/domain-patterns-validation-and-api.md 1.8 KB
- reference/independence-coupling-and-style.md 2.3 KB
- reference/integration-with-plans.md 2.2 KB
- reference/phase-gate-acceptance-checks.md 906 B
- reference/README.md 1.3 KB
- reference/step-keyword-cardinality.md 992 B
- reference/writing-clear-scenarios.md 1.1 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.
- 2d ago First seen · 110 lines · 52 tokens per session scan A 4aff9951ca98
plan-writing-gherkin-criteria is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,013 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.
typescript-test-writing
Use this skill when writing or modifying tests in the llxprt-code repository. Covers mandatory TDD, behavioral testing, bun:test conventions and file naming, mock hygiene (no mock theater), and what never to test. Distilled from dev-docs/RULES.md, which remains the source of truth.
maestro-work
Implement or fix one authorized unit with minimal edits and sufficient evidence. Reuse existing checks and add tests only for concrete uncovered behavior or risk.
typescript-eval
Test TypeScript code snippets before persisting as skills.
Unit Test Scaffold (TypeScript)
Generate TypeScript unit test skeletons (Jest/Vitest) from specifications.