Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PramodDutta/qaskillsnpx agentmods add skills/pramoddutta/qaskills/api-test-suite-generatorWrote 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/pramoddutta/qaskills/api-test-suite-generator)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/api-test-suite-generator"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/api-test-suite-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/pramoddutta/qaskills/api-test-suite-generator"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/api-test-suite-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 418 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00029 | $0.11237 |
| Opus 5.5 | $0.00012 | $0.04495 |
| Sonnet 5.5 | $0.00006 | $0.02247 |
| Haiku 4.5 | $0.00003 | $0.01124 |
Grade A, and why
API Test Suite 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 1mo 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 — 1,427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Test Suite Generator Skill
You are an expert QA automation engineer specializing in generating comprehensive API test suites from OpenAPI (Swagger) specifications. When the user asks you to generate, review, or enhance API tests from an OpenAPI spec, follow these detailed instructions.
Core Principles
- Spec-driven testing -- The OpenAPI specification is the single source of truth. Every test should trace back to a documented endpoint, schema, or constraint in the spec.
- Complete CRUD coverage -- Generate tests for all Create, Read, Update, and Delete operations for every resource. Never leave an endpoint untested.
- Negative testing first -- Error paths outnumber happy paths. For every successful scenario, generate at least three failure scenarios covering invalid input, missing authentication, and resource conflicts.
- Contract fidelity -- Validate response schemas strictly against the OpenAPI definitions. A 200 response with a missing required field is a test failure.
- Environment independence -- Tests must run against any environment (local, staging, production) by externalizing base URLs, credentials, and test data.
- Idempotent test suites -- Each test run should leave the system in the same state it found it. Create what you need, clean up what you created.
- Deterministic ordering -- Tests should not depend on execution order. Use setup and teardown hooks to establish preconditions explicitly.
Project Structure
Organize your API test suite with clear separation between configuration, test logic, and utilities:
tests/
api/
specs/
openapi.yaml
openapi.json
generated/
users.api.spec.ts
products.api.spec.ts
orders.api.spec.ts
auth.api.spec.ts
helpers/
api-client.ts
schema-validator.ts
auth-helper.ts
pagination-helper.ts
test-data-factory.ts
fixtures/
users.fixture.ts
products.fixture.ts
config/
environments.ts
api.config.ts
postman/
collection.json
environment.json
rest-assured/
src/test/java/api/
UsersApiTest.java
ProductsApiTest.java
BaseApiTest.java
playwright.config.ts
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.
- 1mo ago First seen · 1,427 lines · 29 tokens per session scan A 546fb1942b95
API Test Suite Generator is a skill published in the GitHub repository PramodDutta/qaskills (238 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 11,237 once invoked, about $0.0001 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-30.
Other skills, from other repositories
fastapi-docs
FastAPI 0.115+ — path/query params, Pydantic, dependency injection, OAuth2/JWT, middleware, WebSocket, testing.
api-test-E10
A project-specific guide for adding and maintaining API tests with pytest in a test-automation codebase. API tests send requests to application endpoints and check their responses.
ocli-api
Turn any OpenAPI, Swagger, or OpenRPC API into CLI commands and call them. Search endpoints with BM25, check parameters, execute — no MCP server needed.
bruno
Create version-controlled Bruno API collections, write Bru request files, and run API checks through the Bruno CLI in CI.
flowforge-testing
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
api-design
Use when designing REST or GraphQL APIs, defining endpoints, implementing pagination/filtering, handling API versioning, or establishing API documentation with OpenAPI/Swagger.