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 agentmods add skills/kevinnft/ai-agent-skills/api-testingnpx skills add kevinnft/ai-agent-skills --skill api-testinggit clone --depth 1 https://github.com/kevinnft/ai-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/kevinnft/ai-agent-skills/api-testing)<a href="https://agentmods.dev/skills/kevinnft/ai-agent-skills/api-testing"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/api-testing.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01617 |
| Opus 5 | $0.00014 | $0.00809 |
| Sonnet 5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
api-testing 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 yesterday.
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.
### 1. Manual Testing (curl) How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Testing — Automated Endpoint Validation
Test REST and GraphQL APIs with automated validation. Verify endpoints, status codes, response schemas, performance, and security. Ensure API contracts are maintained across changes.
When to Use
- Testing REST/GraphQL endpoints
- Validating API responses
- Contract testing between services
- Performance testing APIs
- Security testing endpoints
- CI/CD API validation
Testing Approaches
1. Manual Testing (curl)
# GET request
curl -X GET https://api.example.com/users
# POST with JSON
curl -X POST https://api.example.com/users \
-H "Content-Type: application/json" \
-d '{"name": "John", "email": "[email protected]"}'
# With authentication
curl -X GET https://api.example.com/profile \
-H "Authorization: Bearer YOUR_TOKEN_HERE"
# Save response
curl -X GET https://api.example.com/users -o response.json
# Show headers
curl -i https://api.example.com/users
# Verbose output
curl -v https://api.example.com/users
2. Automated Testing (Python + requests + pytest)
import requests
import pytest
BASE_URL = "https://api.example.com"
def test_get_users():
response = requests.get(f"{BASE_URL}/users")
# Status code
assert response.status_code == 200
# Response structure
data = response.json()
assert isinstance(data, list)
assert len(data) > 0
# First user structure
user = data[0]
assert "id" in user
assert "name" in user
assert "email" in user
def test_create_user():
payload = {
"name": "John Doe",
"email": "[email protected]"
}
response = requests.post(
f"{BASE_URL}/users",
json=payload
)
assert response.status_code == 201
data = response.json()
assert data["name"] == payload["name"]
assert data["email"] == payload["email"]
assert "id" in data
def test_authentication_required():
response = requests.get(f"{BASE_URL}/profile")
assert response.status_code == 401
def test_invalid_data():
payload = {"name": ""} # Invalid: empty name
response = requests.post(
f"{BASE_URL}/users",
json=payload
)
assert response.status_code == 400
assert "error" in response.json()
def test_not_found():
response = requests.get(f"{BASE_URL}/users/99999")
assert response.status_code == 404
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.
- yesterday First seen · 278 lines · 27 tokens per session scan A 95ab56db7a31
api-testing is a skill published in the GitHub repository kevinnft/ai-agent-skills (13 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,617 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
api-design
Design and implement RESTful APIs with proper routing, validation, error handling, and documentation. Use when building new API endpoints, designing API architecture, or improving existing APIs.
api-testing
Comprehensive API testing, validation, and test suite generation.
create-tutorial
Scaffold a new Membrane API Gateway tutorial in the api-gateway repo — the numbered self-teaching YAML under distribution/tutorials/ /, its support files and README links, and the matching auto-discovered integration test. Use whenever the user asks to create, add, write, or scaffold a tutorial (or a tutorial step)…
optimize-interceptor-docs
Rewrite the reference documentation of a Membrane config element so the page generated at membrane-api.io comes out clean, exact, and reference-style. Use whenever the user wants to write, improve, optimize, polish, or review the docs / Javadoc / @description / @yaml example of an interceptor, plugin, or any…
review-branch
Review the current git branch against master — code quality, refactoring opportunities, regressions, correctness, and test coverage — and print a severity-grouped markdown report. Use whenever the user asks to review the branch, review their changes against master, do a pre-PR / pre-merge review, or asks "is this…
membrane-config
Generate a Membrane API Gateway configuration example or snippet — an apis.yaml (default) or, when explicitly asked, a legacy proxies.xml. Use this whenever the user wants a config, example, or snippet for Membrane: routing a port to a backend, a flow with plugins (setHeader, rateLimiter, basicAuthentication, openapi…