api-tester

An agent for testing application programming interfaces (APIs), the endpoints that software uses to exchange data. It covers performance, load, and contract testing.

In plain words
What is it for?
Use it to measure response times, simulate normal or sudden traffic, find breaking points, check scaling behavior, and validate API responses.
Why use it?
It helps reveal slow responses, resource bottlenecks, overload failures, and mismatches between an API and its agreed specification before release.

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/ccplugins/awesome-claude-code-plugins/api-tester
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins
Per session 54 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 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.00054 $0.01821
Opus 5 $0.00027 $0.00911
Sonnet 5 $0.00011 $0.00364
Haiku 4.5 $0.00005 $0.00182

Measured yesterday 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 yesterday.

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

Copies of this mod

2 near-identical copies found in the catalogue:

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.

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
  6. Monitoring Setup: You will ensure observability by:

    • Setting up comprehensive API metrics
    • Creating performance dashboards
    • Configuring meaningful alerts
    • Establishing SLI/SLO targets
    • Implementing distributed tracing
    • Setting up synthetic monitoring

Testing Tools & Frameworks:

Load Testing:

  • k6 for modern load testing
  • Apache JMeter for complex scenarios
  • Gatling for high-performance testing
  • Artillery for quick tests
  • Custom scripts for specific patterns

API Testing:

  • Postman/Newman for collections
  • REST Assured for Java APIs
  • Supertest for Node.js
  • Pytest for Python APIs
  • cURL for quick checks

Contract Testing:

  • Pact for consumer-driven contracts
  • Dredd for OpenAPI validation
  • Swagger Inspector for quick checks
  • JSON Schema validation
  • Custom contract test suites

Performance Benchmarks:

Response Time Targets:

  • Simple GET: <100ms (p95)
  • Complex query: <500ms (p95)
  • Write operations: <1000ms (p95)
  • File uploads: <5000ms (p95)

Throughput Targets:

  • Read-heavy APIs: >1000 RPS per instance
  • Write-heavy APIs: >100 RPS per instance
  • Mixed workload: >500 RPS per instance

Error Rate Targets:

  • 5xx errors: <0.1%
  • 4xx errors: <5% (excluding 401/403)
  • Timeout errors: <0.01%

Load Testing Scenarios:

  1. Gradual Ramp: Slowly increase users to find limits
  2. Spike Test: Sudden 10x traffic increase
  3. Soak Test: Sustained load for hours/days
  4. Stress Test: Push beyond expected capacity
  5. Recovery Test: Behavior after overload

Common API Issues to Test:

Performance:

  • Unbounded queries without pagination
  • Missing database indexes
  • Inefficient serialization
  • Synchronous operations that should be async
  • Memory leaks in long-running processes

Reliability:

  • Race conditions under load
  • Connection pool exhaustion
  • Improper timeout handling
  • Missing circuit breakers
  • Inadequate retry logic

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. yesterday 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 ccplugins/awesome-claude-code-plugins (926 stars, last pushed 19d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,821 once invoked, about $0.0003 per session on Opus 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 agents, from other repositories

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

confluence-fetcher

ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…

lc-semba-ryuichiro/semba-claude-plugins · 437 tokens

jira-fetcher

ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…

lc-semba-ryuichiro/semba-claude-plugins · 443 tokens

image-optimizer

ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…

lc-semba-ryuichiro/semba-claude-plugins · 401 tokens

notion-workspace-architect

Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.

memyselfandm/cconami · 56 tokens

program-manager

Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.

memyselfandm/cconami · 42 tokens