What is api-isolated-tests?

A tool for making a detailed table of API test cases from an API specification. The table covers normal requests, failures, unusual inputs, and security situations.

Use it to prepare a Markdown test matrix for another tool that generates API tests; it does not generate the test code itself.

It helps ensure important API behaviors are considered before anyone writes test code.

How vlad-ryzhkov/ai-context-engineering-for-qa configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vlad-ryzhkov/ai-context-engineering-for-qa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vlad-ryzhkov/ai-context-engineering-for-qa/main/.claude/skills/api-isolated-tests/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/vlad-ryzhkov/ai-context-engineering-for-qa

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests/github.svg)](https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests)

Your own site

<a href="https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/api-isolated-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,570 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.04570
Opus 5	$0.00028	$0.02285
Sonnet 5	$0.00011	$0.00914
Haiku 4.5	$0.00006	$0.00457

Measured today against content hash 3823b15804c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

api-isolated-tests 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 today.

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.

.claude/skills/api-isolated-tests/SKILL.md · 192 lines

How it starts

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

Recommended Flow

For best results, run /spec-audit first — its audit output enriches scenario generation. Running directly on a specification also works.

Input Context (Process Isolation)

context: fork — you cannot see chat history before your invocation. Allowed inputs: Files explicitly read via tool + $ARGUMENTS path. Forbidden: Assumptions from "previous agent context", inventing spec content.

🔒 SYSTEM REQUIREMENTS

Before execution the agent MUST load: .claude/protocols/gardener.md

Test Scenario Designer (Full Coverage)

Input Strategy (Auto-Discovery)

Source: Search for API specifications in the repository:
- $ARGUMENTS — if a path is substituted here (Claude Code CLI) → read the file with the Read tool.
- User message — if it contains a file path (.md, .yaml, .json, .txt) → read it with the Read tool. (Cursor and other environments where $ARGUMENTS is not substituted.)
- *.yaml, *.json (Swagger/OpenAPI)
- *.proto (gRPC)
- audit/spec-audit-report.md (if exists)
- Ignore audit/test-plan.md (work directly with the specification).
- If no spec found → output to chat: ⚠️ WARNING: No specification found. Please provide a file path or run /spec-audit first. and stop.
Mode: mode: api-integration (DEFAULT) — applies DEFAULT_HEURISTICS to reduce unit-level noise. mode: full-matrix — disables all heuristics, generates exhaustive per-field coverage. Trigger full-matrix when arguments contain full-matrix, full, or exhaustive. Mode is declared in the output file header: > Mode: api-integration or > Mode: full-matrix.
Scope: ALL ENDPOINTS (100% Coverage).
- Do not filter by importance. Test everything: Auth, Business Logic, Dictionaries, Settings.
- Every discovered method (GET/POST/PUT/DELETE) MUST have a set of scenarios.

Verbosity Protocol

SILENT MODE: All content goes to docs/api-isolated-tests/test-scenarios.md, not to chat.

Read the full file on GitHub · 192 lines

Files

What ships with it

4 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.

today Changed · +168 lines · +40 tokens per session 3823b15804c8
9d ago First seen · 24 lines · 17 tokens per session scan A 2db0784823a8

Subscribe to this mod's changes

api-isolated-tests is a skill published in the GitHub repository vlad-ryzhkov/ai-context-engineering-for-qa (6 stars, last pushed today), licensed Unlicense. It adds 57 tokens to every session and 4,570 once invoked, about $0.0003 per session on Opus 5. 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-08-31.

Backend and APIs Testing ai api-testing automation claude context-engineering kotlin

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

detecting-broken-object-property-level-authorization

Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.

xalgorix/xalgorix · 36 tokens

testing

Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…

Skyvern-AI/skyvern · 71 tokens

ai-context-engineering-for-qa: Skill for Claude Code