test-endpoint

test-endpoint is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 0 tokens per session (410 once invoked), scanned A, original, Apache-2.0.

A procedure for testing a web API endpoint with valid requests, invalid input, authentication failures, edge cases, and repeated requests.

In plain words
What is it for?
Sending requests with curl or fetch, checking response status, headers, bodies, and timing, and producing a pass-or-fail summary for each test scenario.
Why use it?
It checks more than the successful response, helping reveal incorrect status codes, inconsistent errors, timing issues, and accidental exposure of sensitive data.

Command

Part of the api-tester plugin — 2 commands shipped together

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/test-endpoint
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install api-tester, the plugin that ships this one along with the rest of its 2 commands.

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 test-endpoint

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00000 $0.00410
Opus 5 $0.00000 $0.00205
Sonnet 5 $0.00000 $0.00082
Haiku 4.5 $0.00000 $0.00041

Measured 4d ago against content hash d35b92ba4875, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-endpoint 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 4d 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.

- Send the request using `curl` or `fetch`.
plugins/api-tester/commands/test-endpoint.md · 48 lines

What it actually says

Test an API endpoint with various request scenarios and validate responses.

Steps

  1. Parse the endpoint specification:
    • URL, HTTP method, headers, authentication.
    • Request body (JSON, form data, multipart).
    • Expected response status and body schema.
  2. Generate test scenarios:
    • Happy path: Valid request with expected response.
    • Validation: Missing required fields, invalid types, out-of-range values.
    • Auth: Missing token, expired token, insufficient permissions.
    • Edge cases: Empty body, very large payload, special characters.
    • Idempotency: Repeated identical requests produce consistent results.
  3. Execute each test:
    • Send the request using curl or fetch.
    • Capture response status, headers, body, and timing.
    • Validate against expected results.
  4. Check response quality:
    • Correct content type header.
    • Consistent error format across failure cases.
    • Proper HTTP status codes (not 200 for errors).
    • No sensitive data in error responses.
  5. Generate a test summary with pass/fail for each scenario.

Format

API Test: <METHOD> <endpoint>

| Scenario | Status | Expected | Actual | Time | Result |
|----------|--------|----------|--------|------|--------|
| Valid request | 200 | 200 | 200 | 45ms | PASS |
| Missing auth | 401 | 401 | 401 | 12ms | PASS |
| Invalid body | 400 | 400 | 500 | 23ms | FAIL |

Pass: <N>/<total>
Issues: <list of failures>

Rules

  • Test authentication and authorization for every endpoint.
  • Verify error responses do not leak stack traces or internal details.
  • Check that CORS headers are set correctly for browser-accessible APIs.
  • Test with realistic payloads, not minimal test data.
  • Verify rate limiting works as documented.
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. 4d ago First seen · 48 lines · 0 tokens per session scan A d35b92ba4875

Subscribe to this mod's changes

test-endpoint is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 410 tokens. 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.