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 omnigentx/jarvis --skill api-testinggit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/api-testing)<a href="https://agentmods.dev/skills/omnigentx/jarvis/api-testing"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/api-testing/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/omnigentx/jarvis/api-testing"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/api-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00907 |
| Opus 5.5 | $0.00020 | $0.00363 |
| Sonnet 5.5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
api-testing 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Testing
Test backend APIs using pytest + httpx (integration) or FastAPI TestClient (unit). Write tests to /tmp, execute via python.
Decision Tree
API to test → Is it a FastAPI app?
├─ Yes → Use TestClient (no server needed)
│ from fastapi.testclient import TestClient
│
└─ No → Use httpx (server must be running)
import httpx
FastAPI TestClient (Unit Tests)
# /tmp/test_api.py
import pytest
from fastapi.testclient import TestClient
from server import app # Import your FastAPI app
client = TestClient(app)
def test_health():
r = client.get("/health")
assert r.status_code == 200
def test_create_item():
r = client.post("/items", json={"name": "test", "price": 9.99})
assert r.status_code == 201
data = r.json()
assert data["name"] == "test"
assert "id" in data
def test_auth_required():
r = client.get("/protected")
assert r.status_code == 401
def test_with_auth():
r = client.get("/protected", headers={"Authorization": "Bearer test-token"})
assert r.status_code == 200
httpx (Integration Tests)
# /tmp/test_integration.py
import httpx
import pytest
BASE_URL = "http://localhost:8000" # Adjust to target
def test_endpoint_responds():
r = httpx.get(f"{BASE_URL}/health")
assert r.status_code == 200
def test_crud_flow():
# Create
r = httpx.post(f"{BASE_URL}/items", json={"name": "test"})
assert r.status_code == 201
item_id = r.json()["id"]
# Read
r = httpx.get(f"{BASE_URL}/items/{item_id}")
assert r.status_code == 200
# Delete
r = httpx.delete(f"{BASE_URL}/items/{item_id}")
assert r.status_code == 204
Execution
# Run all tests
cd <project_dir> && python -m pytest /tmp/test_api.py -v
# Run with coverage
cd <project_dir> && python -m pytest /tmp/test_api.py --cov=. --cov-report=term
Testing Patterns
| Pattern | When | Example |
|---|---|---|
| Happy path | Always first | POST /items → 201 |
| Error scenarios | Required | Invalid input → 422, Not found → 404 |
| Auth flows | If protected | No token → 401, Bad token → 403 |
| Edge cases | Important | Empty body, large payload, special chars |
| Contract validation | API changes | Verify response schema matches spec |
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 · 136 lines · 51 tokens per session scan A 61348eb880f5
api-testing is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 907 once invoked, about $0.0002 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
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
enterprise-integration-testing
Use when testing enterprise integrations across SAP, middleware, WMS, or backend systems, validating E2E enterprise flows, testing SAP-specific patterns (RFC, BAPI, IDoc, OData, Fiori), or enforcing cross-system quality gates.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
selenide-skill
Generates Selenide tests in Java. Concise UI testing framework built on Selenium with automatic waits and fluent API. Use when user mentions "Selenide", "$(selector)", "shouldBe(visible)", "Selenide Java". Triggers on: "Selenide", "$() selector", "shouldBe", "shouldHave", "Selenide test".