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 cuongtl1992/vibe-skills --skill cucumber-api-tests-generatorgit clone --depth 1 https://github.com/cuongtl1992/vibe-skillsWrote 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/cuongtl1992/vibe-skills/cucumber-api-tests-generator)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/cucumber-api-tests-generator"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/cucumber-api-tests-generator/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/cuongtl1992/vibe-skills/cucumber-api-tests-generator"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/cucumber-api-tests-generator.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.00143 | $0.01748 |
| Opus 5.5 | $0.00057 | $0.00699 |
| Sonnet 5.5 | $0.00029 | $0.00350 |
| Haiku 4.5 | $0.00014 | $0.00175 |
Grade A, and why
cucumber-api-tests-generator 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 2mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cucumber API Tests Generator
Generate TypeScript step definitions and API Client classes from Cucumber feature files for REST API testing.
Workflow Overview
- Parse feature file → Extract API scenarios and steps
- Analyze API operations → Identify endpoints, methods, request/response schemas
- Check existing implementations → Avoid duplicates
- Generate API Client class → Typed HTTP client with methods per endpoint
- Generate step definitions → Given/When/Then with axios/supertest calls
- Generate type models → Request/Response TypeScript interfaces
Step 1: Parse Feature File
Read the .feature file and extract API-specific information:
- Feature name and description
- Background steps (auth setup, base URL, etc.)
- All scenarios with steps
- HTTP methods (GET, POST, PUT, DELETE, PATCH)
- Endpoint paths (e.g.,
/api/v1/products) - Request parameters (path, query, body, headers)
- Expected response status codes and body fields
- Data tables (request payload, expected fields)
// Example parsed API scenario
interface ParsedApiScenario {
name: string;
tags: string[]; // @smoke, @regression, @auth
steps: Array<{
keyword: 'Given' | 'When' | 'Then' | 'And';
text: string;
dataTable?: Record<string, string>[];
docString?: string; // JSON body as doc string
}>;
}
Step 2: Analyze API Operations
Identify from the steps:
| Pattern in step | Inference |
|---|---|
| "I send a GET request to {string}" | GET method, dynamic URL |
| "I call the {string} API with body:" | POST/PUT, has request body |
| "the response status should be {int}" | Status assertion |
| "the response should contain {string}" | Body field assertion |
| "I am authenticated as {string}" | Auth setup needed |
| "I set header {string} to {string}" | Custom request headers |
Step 3: Check Existing Implementations
Scan project for existing API step files:
# Check existing step definitions
grep -r "Given\|When\|Then" src/step_definitions/api/*.ts 2>/dev/null || echo "No API steps found"
# Check existing API clients
ls src/support/api_clients/ 2>/dev/null || echo "No API clients found"
What ships with it
3 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.
- 2mo ago First seen · 210 lines · 143 tokens per session scan A 7dfa374f5145
cucumber-api-tests-generator is a skill published in the GitHub repository cuongtl1992/vibe-skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 143 tokens to every session and 1,748 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.