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 LambdaTest/agent-skills --skill api-to-testcase-generatorgit clone --depth 1 https://github.com/LambdaTest/agent-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/lambdatest/agent-skills/api-to-testcase-generator)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/api-to-testcase-generator"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-to-testcase-generator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 145 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 155 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 160 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 219 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00182 | $0.02377 |
| Opus 5 | $0.00091 | $0.01189 |
| Sonnet 5 | $0.00036 | $0.00475 |
| Haiku 4.5 | $0.00018 | $0.00238 |
Grade A, and why
api-to-testcase-generator scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
when the user shares an OpenAPI file, Swagger YAML/JSON, Postman collection, curl commands, or How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API-to-Test Case Generator
Converts API definitions into production-ready test suites covering happy paths, edge cases, error handling, and boundary conditions.
Supported Input Formats
| Format | Example |
|---|---|
| OpenAPI 3.x YAML/JSON | openapi: 3.0.0 |
| Swagger 2.0 | swagger: "2.0" |
| Postman Collection v2.x | JSON export from Postman |
| Raw curl commands | curl -X POST https://... |
| Plain English description | "POST /users creates a user with name and email" |
| HTTP request/response examples | Paste raw request + response |
| Code (route handlers / controllers) | Express.js, FastAPI, Spring, etc. |
Supported Test Frameworks
| Language | Frameworks |
|---|---|
| Python | pytest + requests or httpx |
| JavaScript/TypeScript | Jest, Mocha/Chai, Supertest |
| Java | JUnit 5 + RestAssured |
| Go | testing + net/http/httptest |
| API-level (language-agnostic) | Newman (Postman), k6 (load), plain .http files |
If the user doesn't specify a framework, ask — or default to pytest for Python APIs, Jest for JS/TS APIs.
Workflow
Step 1 — Parse the API Definition
Extract from the input:
- Endpoints: method + path (e.g.,
POST /api/v1/users) - Request: headers, query params, path params, body schema (required vs optional fields, types)
- Response: status codes, response body schema, headers
- Auth: Bearer token, API key, Basic auth, OAuth2
- Constraints: min/max, enum values, format (email, uuid, date-time), nullable
If input is ambiguous or incomplete, ask the user to clarify before generating.
Step 2 — Determine Test Strategy
For each endpoint, generate tests across these categories:
✅ Happy Path Tests
- Valid request with all required fields → expect
2xx - Valid request with all optional fields included
- Minimal valid request (required fields only)
❌ Validation / Error Tests
- Missing required fields → expect
400/422 - Invalid field types (string where int expected, etc.)
- Out-of-range values (below min, above max)
- Invalid enum values
- Malformed request body (invalid JSON)
- Extra/unknown fields (if strict validation expected)
What ships with it
2 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.
- 9d ago First seen · 274 lines · 182 tokens per session scan A 217df0ab6faf
api-to-testcase-generator is a skill published in the GitHub repository LambdaTest/agent-skills (366 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 2,377 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
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…
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
data-strategy
Test data strategy for the Playwright scaffold — Faker + Zod factories for dynamic happy-path data, static TS files (.ts with as const exports — never .json) for domain-specific curated invalid sets, and the universal type-mismatch arrays in test-data/static/util/invalid-values.ts. Use when creating or editing a data…
helpers
Plain utility function conventions for the Playwright scaffold — app-specific helpers in helpers/{area}/ (authentication bootstrap, storage-state creation, data seeding) and generic utilities in helpers/util/ (date formatting, string manipulation, parsing). Use when adding a reusable function that does NOT need the…