smoke-test-api

smoke-test-api is a skill for Claude Code from FortiumPartners/ensemble. It costs 0 tokens per session (1,599 once invoked), scanned A, original, MIT.

A skill for smoke-testing APIs, which means quickly checking that important endpoints are available and behaving correctly. It checks health, response times, status codes, response data, errors, and core operations.

In plain words
What is it for?
It is for validating API health, critical CRUD, search and authentication endpoints, performance targets, and behavior across environments.
Why use it?
It helps reveal unavailable services or broken endpoints before and after deployments, rollbacks, and other release events.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ensemble-e2e-testing plugin — 7 skills, 1 agent shipped together

Good fit It is for validating API health, critical CRUD, search and authentication endpoints, performance targets, and behavior across environments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fortiumpartners/ensemble/smoke-test-api
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.

Any agent
npx skills add FortiumPartners/ensemble --skill smoke-test-api
Clone the repo
git clone --depth 1 https://github.com/FortiumPartners/ensemble

Made for: Claude Code.

Or install ensemble-e2e-testing, the plugin that ships this one along with the rest of its 7 skills, 1 agent.

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 smoke-test-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/fortiumpartners/ensemble/smoke-test-api.svg)](https://agentmods.dev/skills/fortiumpartners/ensemble/smoke-test-api)
Your own site
<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/smoke-test-api"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/smoke-test-api.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01599
Opus 5 $0.00000 $0.00800
Sonnet 5 $0.00000 $0.00320
Haiku 4.5 $0.00000 $0.00160

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

Security

Grade A, and why

smoke-test-api scanned grade A with 0 findings 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/execute-health-checks.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/e2e-testing/skills/smoke-test-api/SKILL.md · 232 lines

How it starts

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

Smoke Test API Skill

Quick Reference - Load this first for fast context (~3KB)

Mission

Execute comprehensive API health smoke tests to validate service availability, response times, and critical endpoint functionality during release workflows.

Core Capabilities

  • Health Check Execution: Test API endpoints for availability and response time
  • Critical Endpoint Validation: Verify core API operations (CRUD, search, auth)
  • Response Validation: Check status codes, response structure, error handling
  • Performance SLA Validation: Ensure response times meet performance budgets
  • Multi-Environment Support: Test across pre-release, staging, production environments

When to Use This Skill

Use this skill when:

  • Executing pre-release smoke tests (before staging deployment)
  • Validating post-deployment health (after staging/production deployment)
  • Testing canary deployments (5%, 25%, 100% traffic)
  • Verifying rollback success (after rollback operations)
  • Running scheduled health checks (monitoring integration)

Quick Start

1. Load Skill in Agent

skills:
  - name: smoke-test-api
    path: skills/smoke-test-api/SKILL.md

2. Execute Health Checks

const { SmokeTestAPI } = require('./scripts/execute-health-checks.js');

const tester = new SmokeTestAPI({
  baseUrl: 'https://staging.example.com',
  timeout: 5000,
  retries: 2
});

const result = await tester.executeHealthChecks({
  environment: 'staging',
  endpoints: [
    { path: '/health', method: 'GET', expectedStatus: 200 },
    { path: '/api/v1/users', method: 'GET', expectedStatus: 200 }
  ]
});

if (result.passed) {
  console.log('✅ API health checks passed');
} else {
  console.error('❌ API health checks failed');
}

3. Configuration Template

environment: staging
baseUrl: https://staging.example.com
timeout: 5000
retries: 2
endpoints:
  - name: health-check
    path: /health
    method: GET
    expectedStatus: 200
    sla: 100
  - name: list-users
    path: /api/v1/users
    method: GET
    expectedStatus: 200
    sla: 500

Read the full file on GitHub · 232 lines

Files

What ships with it

3 files 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.

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 · 232 lines · 0 tokens per session scan A 3530dce9ebcd

Subscribe to this mod's changes

smoke-test-api is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,599 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

voiden

Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.

VoidenHQ/voiden · 28 tokens

architecture-patterns

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…

yonatangross/orchestkit · 56 tokens

testing-integration

Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.

yonatangross/orchestkit · 49 tokens

csharp-dotnet

Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…

ericrisco/rsc-harness · 89 tokens

nestjs

Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…

ericrisco/rsc-harness · 81 tokens

nodejs

Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…

ericrisco/rsc-harness · 77 tokens