api-test

api-test is a skill for Claude Code from xvirobotics/metaskill. It costs 32 tokens per session (1,002 once invoked), scanned A, original, MIT.

A tool for running API integration tests against a live backend. API integration tests check that software endpoints return the expected responses and status codes.

In plain words
What is it for?
Use it after starting or deploying a backend to check its health, run integration tests, and manually verify important endpoints.
Why use it?
It verifies that the running server actually works from the outside, rather than only checking isolated code.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it after starting or deploying a backend to check its health, run integration tests, and manually verify important endpoints.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xvirobotics/metaskill/api-test
Install

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.

Any agent
npx skills add xvirobotics/metaskill --skill api-test
Clone the repo
git clone --depth 1 https://github.com/xvirobotics/metaskill

Made for: Claude Code.

Wrote 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.

agentmods badge for api-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/xvirobotics/metaskill/api-test/github.svg)](https://agentmods.dev/skills/xvirobotics/metaskill/api-test)
Your own site
<a href="https://agentmods.dev/skills/xvirobotics/metaskill/api-test"><img src="https://agentmods.dev/badge/skills/xvirobotics/metaskill/api-test/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.

agentmods 80×15 button for api-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/xvirobotics/metaskill/api-test"><img src="https://agentmods.dev/badge/skills/xvirobotics/metaskill/api-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,002 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01002
Opus 5.5 $0.00013 $0.00401
Sonnet 5.5 $0.00006 $0.00200
Haiku 4.5 $0.00003 $0.00100

Measured 1mo ago against content hash 1c5a7f2c2208, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-test 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf http://localhost:3000/api/health && echo "Server is healthy" || echo "Server is not responding"
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • api-test — 100% identical, 0 lines differ
examples/fullstack-web/.claude/skills/api-test/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an API integration test agent. Your job is to verify that all API endpoints are responding correctly by running integration tests against a live server.

Current State

Current branch: !git branch --show-current Recent changes: !git diff --name-only HEAD~3 2>/dev/null || echo "fewer than 3 commits"

Test Procedure

Step 1: Verify Server is Running

curl -sf http://localhost:3000/api/health && echo "Server is healthy" || echo "Server is not responding"

If the server is not running, report that the server must be started first (with npm run dev or /deploy-preview) and stop.

Step 2: Run Integration Tests

Run the API integration test suite:

DATABASE_URL="${DATABASE_URL_TEST:-postgresql://test:test@localhost:5432/myapp_test}" npx vitest run --config vitest.integration.config.ts 2>/dev/null || npx vitest run tests/integration/ 2>/dev/null || npx vitest run --grep "integration|api|endpoint"

If a dedicated integration test config or directory exists, use it. Otherwise, run tests that match integration/API patterns.

Step 3: Manual Endpoint Verification

If integration tests are not set up yet, manually verify key endpoints:

Health Check:

curl -s -w "\nHTTP_STATUS:%{http_code}" http://localhost:3000/api/health

Auth Endpoints (if they exist):

# Register
curl -s -w "\nHTTP_STATUS:%{http_code}" -X POST http://localhost:3000/api/auth/register \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","password":"TestPass123!","name":"Test User"}'

# Login
curl -s -w "\nHTTP_STATUS:%{http_code}" -X POST http://localhost:3000/api/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","password":"TestPass123!"}'

List Endpoints (verify pagination):

curl -s -w "\nHTTP_STATUS:%{http_code}" http://localhost:3000/api/users?page=1&limit=10

Validation Testing (send invalid data):

curl -s -w "\nHTTP_STATUS:%{http_code}" -X POST http://localhost:3000/api/auth/register \
  -H "Content-Type: application/json" \
  -d '{"email":"not-an-email"}'

Read the full file on GitHub · 116 lines

Changes

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.

  1. 1mo ago First seen · 116 lines · 32 tokens per session scan A 1c5a7f2c2208

Subscribe to this mod's changes

api-test is a skill published in the GitHub repository xvirobotics/metaskill (73 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,002 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

api-test

Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.

morganmuli/metaskill · 32 tokens

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.

laolaoshiren/claude-code-skills-zh · 86 tokens

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.

hoangsonww/Claude-Code-Agent-Monitor · 80 tokens

playwright

Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.

Mindrally/skills · 26 tokens

browser-test-loop

Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.

OneWave-AI/claude-skills · 74 tokens

cypress

Cypress end-to-end testing best practices for web applications, covering test structure, commands, and reliability patterns.

Mindrally/skills · 25 tokens