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/morganmuli/metaskill/api-testnpx skills add morganmuli/metaskill --skill api-testgit clone --depth 1 https://github.com/morganmuli/metaskillWhat 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.00032 | $0.01002 |
| Opus 5 | $0.00016 | $0.00501 |
| Sonnet 5 | $0.00006 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
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 2d 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" 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.
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"}'
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.
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.
- 2d ago First seen · 116 lines · 32 tokens per session scan A 1c5a7f2c2208
api-test is a skill published in the GitHub repository morganmuli/metaskill (1 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 1,002 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
generate-report
Generate a comprehensive summary report of the latest experiment including metrics, plots, and comparison with baseline. Use this after training and evaluation to create a shareable experiment summary.
evaluate-model
Load the latest model checkpoint, run evaluation on the test set, and generate a metrics report with confusion matrix. Use this after training to assess model performance or to re-evaluate a specific checkpoint.
run-pipeline
Run the full data science pipeline: validate raw data, preprocess, engineer features, train model, and evaluate. Use this when you want to execute the end-to-end ML pipeline or re-run it after data or code changes.
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.
run-simulator
Build and launch the app in the iOS Simulator. Automatically selects an appropriate simulator device, boots it if needed, and installs and launches the app.
deploy-preview
Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.