api-test

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

A test agent for checking API endpoints, which are server URLs that applications use to exchange data.

In plain words
What is it for?
Use it to check server health, run API integration tests, and manually test important endpoints when automated tests are unavailable.
Why use it?
It verifies that a running backend responds correctly instead of relying only on code inspection.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to check server health, run API integration tests, and manually test important endpoints when automated tests are unavailable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/morganmuli/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 morganmuli/metaskill --skill api-test
Clone the repo
git clone --depth 1 https://github.com/morganmuli/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/morganmuli/metaskill/api-test/github.svg)](https://agentmods.dev/skills/morganmuli/metaskill/api-test)
Your own site
<a href="https://agentmods.dev/skills/morganmuli/metaskill/api-test"><img src="https://agentmods.dev/badge/skills/morganmuli/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/morganmuli/metaskill/api-test"><img src="https://agentmods.dev/badge/skills/morganmuli/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 100% copy Near-identical to another mod 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

This is a copy

100% identical to api-test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 morganmuli/metaskill (1 stars, last pushed 5d 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). It is 100% identical to api-test, differing in 0 lines, and is treated as a copy.

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.

xvirobotics/metaskill · 32 tokens

verify

Verify-before-done — exercise the current change end-to-end against its acceptance criteria (the SDD plan's, or the ticket's) and report a per-criterion PASS/FAIL verdict, then record the outcome to memory. This is the concrete action that satisfies moflo's verify-before-done gate (gates.verifybeforedone / /flo -v /…

eric-cielo/moflo · 122 tokens

api-harness

Use the API harness to drive Agentweaver through its REST API, capture the complete request/response evidence, and emit a normalized agentweaver.persona-judge-verdict/v1 JSON verdict. It is for backend/API end-to-end validation; use the UI or MCP harness for those surfaces.

sabbour/agentweaver · 0 tokens

yellow-sheet-corpus

Run the Yellow Sheet chain end to end against ANY matter, from the original PDFs, and read the result honestly. Use whenever someone asks what has been tested end to end, whether a matter produces a usable sheet, how to onboard a NEW matter, or asks to re-run after a code change. Carries the intake mechanism that…

shawnclybor/clybor-claude-tooling · 173 tokens

build-and-test

Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.

xvirobotics/metaskill · 31 tokens

deploy-preview

Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.

xvirobotics/metaskill · 26 tokens