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 oumaimah-QA/QIOS --skill gherkin-spec-writergit clone --depth 1 https://github.com/oumaimah-QA/QIOSWrote 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/oumaimah-qa/qios/gherkin-spec-writer)<a href="https://agentmods.dev/skills/oumaimah-qa/qios/gherkin-spec-writer"><img src="https://agentmods.dev/badge/skills/oumaimah-qa/qios/gherkin-spec-writer/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/oumaimah-qa/qios/gherkin-spec-writer"><img src="https://agentmods.dev/badge/skills/oumaimah-qa/qios/gherkin-spec-writer.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.00129 | $0.01033 |
| Opus 5 | $0.00064 | $0.00517 |
| Sonnet 5 | $0.00026 | $0.00207 |
| Haiku 4.5 | $0.00013 | $0.00103 |
Grade A, and why
gherkin-spec-writer 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 11d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gherkin Spec Writer
Purpose
Generate clean, structured, executable Gherkin .feature files from any requirement.
Ready to use with Cucumber, Behave, Karate, or any BDD framework.
Input Accepted
- User Story (As a / I want / So that)
- Acceptance criteria (bullet points or draft Given/When/Then)
- Plain feature description in natural language
- Existing test cases to convert to Gherkin format
- API endpoint or UI flow description
Generation Process
Step 1 — Extract Scenarios
Identify each distinct test scenario:
- Minimum: 1 happy path
- 1 negative per business rule
- 1 boundary scenario per numeric or date field
- 1 security/auth scenario if authentication is involved
Step 2 — Identify Shared Context
Extract repeated Given steps shared by all scenarios → move to Background.
If a precondition applies only to some scenarios, keep it inside those scenarios.
Step 3 — Group Data-Driven Cases
Identify 3+ similar scenarios that differ only by input values → use Scenario Outline + Examples.
Step 4 — Apply Tags
Tag each scenario using the convention in references/gherkin-tags.md.
Gherkin Structure
Feature: [Short feature name — noun phrase]
As a [role]
I want [action]
So that [benefit]
Background:
Given [shared precondition — max 3 steps]
And [shared precondition]
@smoke @critical
Scenario: [Descriptive title — what is being tested]
Given [initial state — system or user context]
When [single action performed by the actor]
Then [observable, verifiable outcome]
And [additional outcome if needed]
@negative @high
Scenario: [Negative case title]
Given [context]
When [invalid action or bad condition]
Then [error or rejection outcome]
@boundary @regression
Scenario Outline: [Title with <variable>]
Given [context with <variable>]
When [action with <variable>]
Then [result is <expected>]
Examples:
| variable | expected |
| value1 | result1 |
| value2 | result2 |
| value3 | result3 |
What ships with it
6 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.
- 11d ago First seen · 139 lines · 129 tokens per session scan A d66f564eb87e
gherkin-spec-writer is a skill published in the GitHub repository oumaimah-QA/QIOS (3 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 1,033 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
Cypress E2E Testing
Cypress end-to-end testing with custom commands, intercepts, and component testing.
Playwright E2E Testing
Comprehensive Playwright end-to-end testing patterns with Page Object Model, fixtures, and best practices.
api-testing
API testing patterns for Playwright -- apiRequest fixture usage, Zod response schema creation and validation, test.step wrapping for multi-call tests, per-field negative/validation testing, path parameter fuzzing, and helper fixtures for shared setup/teardown. Use when writing or updating API test specs, adding tests…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
test-standards
Spec file conventions for the Playwright scaffold — imports from test-options.ts, test file structure (describe / beforeEach / test / test.step), single-tag rule, functional vs E2E vs API vs setup test types, data-driven test loops against TS static data, web-first assertions, destructive-test cleanup, and test…