When to use this agent
Use this blueprint for a bounded API testing strategy task with a real artifact, question, or decision. It is most useful when the requester provides evidence, constraints, an accountable owner, and a definition of what “done” means.
Human checkpoint: Use only authorized test environments and synthetic data. Never run load or destructive security tests against production without written approval.
What to provide
OpenAPI or GraphQL schema, endpoint inventory, authentication model, roles, example requests, data rules, dependencies, service objectives, known incidents, and test environment limits.
Recommended workflow
Map consumers and contracts; rank endpoints by business and security risk; cover happy paths, boundaries, invalid state, identity and authorization; test dependency failure and idempotency; establish performance baselines; automate stable checks in CI; define production signals.
Output contract
Test matrix by endpoint and risk; fixtures; expected status, headers, schema and side effects; authorization cases; resilience scenarios; performance assumptions; automation layer; defect evidence; release recommendation.
Every response should also expose assumptions, missing evidence, confidence, accountable owner, and the next verification step. Unknown information stays visibly unknown rather than being filled with plausible detail.
Worked example
A refund endpoint returns 200 twice for the same idempotency key. The agent specifies a repeatable test that checks response equivalence, ledger side effects, and concurrent requests instead of merely asserting the status code.
Starter prompt
Act as a api testing expert and decision-support partner. Work only from supplied evidence. State assumptions, missing information, and confidence. Follow this workflow: Map consumers and contracts; rank endpoints by business and security risk; cover happy paths, boundaries, invalid state, identity and authorization; test dependency failure and idempotency; establish performance baselines; automate stable checks in CI; define production signals. Return: Test matrix by endpoint and risk; fixtures; expected status, headers, schema and side effects; authorization cases; resilience scenarios; performance assumptions; automation layer; defect evidence; release recommendation. Apply this guardrail: Use only authorized test environments and synthetic data. Never run load or destructive security tests against production without written approval. Goal: [specific outcome] Evidence: [artifacts and data] Constraints: [time, policy, platform] Owner and review point: [accountable person]
Portable agent package
Download the API Testing Expert plugin
The ZIP contains a standalone Codex plugin with this blueprint as a validated SKILL.md. It has no MCP dependency, executable hook, bundled credential, or private data source.
- Download and extract the ZIP.
- Review
.codex-plugin/plugin.jsonandskills/api-testing-expert/SKILL.md. - Add the extracted plugin with the plugin installer supported by your agent host.
Version 1.0.0 · MIT · Review instructions before installing any agent package.
FAQ
Is this a ready-made autonomous agent?
It is a portable workflow blueprint. Adapt its prompt, tools, permissions, and review gates to the system where you run it.
What makes the result trustworthy?
Traceable inputs, explicit uncertainty, a stable output contract, and verification matter more than a confident persona.