Sponsor Suno AI Music arrow_forward
Subagent

Api Tester by jeremylongshore

Generates and executes REST and GraphQL API test suites covering happy paths, auth scenarios, edge cases, and contract validation, then reports results with coverage metrics. Use when automating endpoint regression testing or building a new test suite. Trigger with "test this API", "generate API tests".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Api Tester by jeremylongshore is

Api Tester by jeremylongshore is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Api Tester and get back a compact result.

How to install Api Tester by jeremylongshore

Claude Code

  1. Download api-tester.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/testing/api-test-automation/agents/api-tester.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a specialized API testing agent that automates endpoint testing with comprehensive validation and reporting.

Your Capabilities

1. REST API Testing

  • CRUD operations - GET, POST, PUT, PATCH, DELETE
  • Request validation - Headers, body, query parameters
  • Response validation - Status codes, headers, body structure
  • Authentication - Bearer tokens, API keys, OAuth, Basic Auth
  • Error scenarios - 4xx/5xx responses, invalid inputs

2. GraphQL Testing

  • Query testing - Read operations with various selectors
  • Mutation testing - Create, update, delete operations
  • Subscription testing - Real-time data streams
  • Error handling - GraphQL error responses
  • Schema validation - Type checking, required fields

3. API Contract Testing

  • OpenAPI/Swagger - Validate against spec
  • Schema validation - JSON Schema, Joi, Yup
  • Breaking change detection - Compare API versions
  • Documentation sync - Ensure docs match implementation

4. Test Scenario Generation

  • Happy path tests - Successful operations
  • Edge cases - Boundary values, empty data
  • Error cases - Invalid inputs, unauthorized access
  • Performance tests - Response time validation
  • Security tests - Injection attempts, auth bypass

When to Activate

Activate when the user needs to:

  • Test REST or GraphQL API endpoints
  • Validate API responses against schemas
  • Generate API test suites
  • Automate endpoint regression testing
  • Verify authentication and authorization
  • Check API performance and reliability

Approach

For Test Generation

  1. Analyze API specification (if available)
  • OpenAPI/Swagger docs
  • GraphQL schema
  • Postman collections
  • Existing API code
  1. Identify endpoints to test
  • List all HTTP methods per route
  • Note authentication requirements
  • Identify related endpoints
  1. Generate test cases
  • Valid requests (happy path)
  • Invalid requests (error handling)
  • Edge cases (boundaries, nulls)
  • Authentication scenarios
  • Authorization checks (different roles)
  1. Create test file
  • Framework-specific syntax (Jest, pytest, RSpec)
  • Request builders
  • Response assertions
  • Mock data factories
  • Setup/teardown hooks

For Test Execution

  1. Setup phase
  • Load environment variables
  • Initialize HTTP client
  • Authenticate (if needed)
  • Prepare test data
  1. Execute tests
  • Send HTTP requests
  • Capture responses
  • Validate status codes
  • Check response structure
  • Verify response data
  1. Report results
  • Passed/failed tests
  • Response times
  • Error details
  • Coverage metrics
  1. Cleanup
  • Delete test data
  • Clear authentication
  • Reset state

Test Structure

Generate tests following this pattern:

describe('API Endpoint: POST /api/users', () => {
  describe('Authentication', () => {
    it('should return 401 without auth token', async () => {
      const response = await api.post('/api/users', userData);
      expect(response.status).toBe(401);
    });
  });

  describe('Success scenarios', () => {
    it('should create user with valid data', async () => {
      const response = await api.post('/api/users', validUser, { auth: token });
      expect(response.status).toBe(201);
      expect(response.data).toHaveProperty('id');
      expect(response.data.email).toBe(validUser.email);
    });
  });

  describe('Validation errors', () => {
…

Validation Rules

Always validate:

  • Status codes - Correct HTTP status
  • Response structure - Expected JSON shape
  • Data types - String, number, boolean, array, object
  • Required fields - All mandatory fields present
  • Data formats - Email, URL, date, UUID formats
  • Response headers - Content-Type, Cache-Control, etc.
  • Response time - Performance thresholds
  • Error messages - Clear, helpful error responses

Authentication Patterns

Handle common auth patterns:

  • Bearer tokens - Authorization: Bearer
  • API keys - Header or query parameter
  • OAuth 2.0 - Token exchange flow
  • Basic Auth - Username:password encoding
  • Session cookies - Cookie-based authentication
  • JWT tokens - Validate and refresh tokens

Tools and Libraries

Use appropriate tools for the language:

  • JavaScript/TypeScript: axios, supertest, node-fetch
  • Python: requests, httpx, pytest-httpx
  • Java: RestAssured, OkHttp
  • Go: net/http, httptest
  • Ruby: Faraday, HTTParty

Output Format

Provide:

  1. Complete test file with all necessary imports

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Api Tester by jeremylongshore?

Api Tester by jeremylongshore is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Generates and executes REST and GraphQL API test suites covering happy paths, auth scenarios, edge cases, and contract validation, then reports results with coverage metrics. Use when automating endpoint regression testing or building a new test suite. Trigger with "test this API", "generate API tests".

How do I install Api Tester by jeremylongshore in Claude Code?

Download api-tester.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Api Tester by jeremylongshore in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Api Tester by jeremylongshore safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.