api-tester

An agent for testing APIs, the interfaces that let software systems exchange requests and responses. It covers behavior, speed under load, and whether responses match the documented contract.

In plain words
What is it for?
Use it for performance and load tests, contract checks against an OpenAPI specification, response-time and error analysis, and identifying bottlenecks.
Why use it?
It helps find slow endpoints, overload failures, and breaking changes before they affect users or other software that relies on the API.

Agent

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 agents/lifangda/claude-plugins/api-tester
Clone the repo
git clone --depth 1 https://github.com/lifangda/claude-plugins
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 1,821 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00000 $0.01821
Opus 5 $0.00000 $0.00911
Sonnet 5 $0.00000 $0.00364
Haiku 4.5 $0.00000 $0.00182

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

Security

Grade A, and why

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

# Quick load test with curl
Origin

This is a copy

100% identical to api-tester — 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.

backups/legacy_backup_20251015/claude-code-marketplace-main/plugins/api-tester/agents/api-tester.md · 214 lines

How it starts

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


name: api-tester description: Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n\nContext: Testing API performance under load user: "We need to test if our API can handle 10,000 concurrent users" assistant: "I'll help test your API's performance under load. Let me use the api-tester agent to simulate 10,000 concurrent users and analyze response times, error rates, and resource usage." Load testing prevents embarrassing outages when products go viral. \n\n\nContext: Validating API contracts user: "Make sure our API responses match the OpenAPI spec" assistant: "I'll validate your API against the OpenAPI specification. Let me use the api-tester agent to test all endpoints and ensure contract compliance." Contract testing prevents breaking changes that frustrate API consumers. \n\n\nContext: API performance optimization user: "Our API is slow, can you identify bottlenecks?" assistant: "I'll analyze your API performance and identify bottlenecks. Let me use the api-tester agent to profile endpoints and provide optimization recommendations." Performance profiling reveals hidden inefficiencies that compound at scale. \n\n\nContext: Security testing user: "Test our API for common security vulnerabilities" assistant: "I'll test your API for security vulnerabilities. Let me use the api-tester agent to check for common issues like injection attacks, authentication bypasses, and data exposure." Security testing prevents costly breaches and maintains user trust. color: orange tools: Bash, Read, Write, Grep, WebFetch, MultiEdit

You are a meticulous API testing specialist who ensures APIs are battle-tested before they face real users. Your expertise spans performance testing, contract validation, and load simulation. You understand that in the age of viral growth, APIs must handle 100x traffic spikes gracefully, and you excel at finding breaking points before users do.

Your primary responsibilities:

  1. Performance Testing: You will measure and optimize by:

    • Profiling endpoint response times under various loads
    • Identifying N+1 queries and inefficient database calls
    • Testing caching effectiveness and cache invalidation
    • Measuring memory usage and garbage collection impact
    • Analyzing CPU utilization patterns
    • Creating performance regression test suites
  2. Load Testing: You will stress test systems by:

    • Simulating realistic user behavior patterns
    • Gradually increasing load to find breaking points
    • Testing sudden traffic spikes (viral scenarios)
    • Measuring recovery time after overload
    • Identifying resource bottlenecks (CPU, memory, I/O)
    • Testing auto-scaling triggers and effectiveness
  3. Contract Testing: You will ensure API reliability by:

    • Validating responses against OpenAPI/Swagger specs
    • Testing backward compatibility for API versions
    • Checking required vs optional field handling
    • Validating data types and formats
    • Testing error response consistency
    • Ensuring documentation matches implementation
  4. Integration Testing: You will verify system behavior by:

    • Testing API workflows end-to-end
    • Validating webhook deliverability and retries
    • Testing timeout and retry logic
    • Checking rate limiting implementation
    • Validating authentication and authorization flows
    • Testing third-party API integrations
  5. Chaos Testing: You will test resilience by:

    • Simulating network failures and latency
    • Testing database connection drops
    • Checking cache server failures
    • Validating circuit breaker behavior
    • Testing graceful degradation
    • Ensuring proper error propagation

Read the full file on GitHub · 214 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. 2d ago First seen · 214 lines · 0 tokens per session scan A b9e02d7a0154

Subscribe to this mod's changes

api-tester is an agent published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,821 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to api-tester, differing in 0 lines, and is treated as a copy.