Agent skill

Agent Integration Testing

by av in av/mi

Writes plain-English integration test specs with verifiable steps and expectations, then runs each one through a subagent that reports pass or fail with logs.

No licenceAuto-check passedTesting & QA

Install Agent Integration Testing

skills CLI
$ npx skills add av/mi --skill agent-integration-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install av/mi agent-integration-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/av/mi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-integration-testing .claude/skills/agent-integration-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-integration-testing
GitHub stars
102
Token cost
~908 tokens
SKILL.md length
384 words
Files
2
Skills in repo
20
Repo updated
First seen
Licence
None found

At a glance

Writes plain-English integration test specs with verifiable steps and expectations, then runs each one through a subagent that reports pass or fail with logs.

  • Works in 5 steps: Investigate Codebase Area → Write Test Specification → Define Verifiable Tests → …
  • Writing an integration test plan for a feature before validating it
  • SKILL.md covers Overview, Core Process, Quick Reference and Red Flags - STOP and Start Over, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill investigates the codebase area under test, broadly by default or narrowed with glob and grep when the user names a feature, then writes a test spec file at tests/name.md with a Prerequisites section listing any setup needed, such as environment variables, database seeding or background services. Each test is written in plain English with clear reproduction steps and a set of expectations, and every expectation must be strictly verifiable by an agent using tools such as shell commands, HTTP requests or file reads; an expectation that cannot be checked this way is invalid and has to be rewritten or removed.

Execution spawns one subagent per test, which follows the prerequisites, runs the steps and checks the outcomes against the expectations, with results and logs collected as pass or fail. If the user asks for failures to be fixed, a further subagent, described as an SWE or BUILDER agent, is spawned to investigate and fix them. A short README also lists red flags that should make the process stop and start over.

When your agent uses it

  • Writing an integration test plan for a feature before validating it
  • Running integration tests through subagents and collecting pass or fail results
  • Fixing failures found during an integration test run

Example prompts

  • “Write an integration test spec for the checkout flow and run it through subagents.”
  • “Investigate the auth module and create verifiable tests for the login endpoint.”
  • “Run the integration tests in tests/integration.md and fix any failures.”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Investigate Codebase Area
  2. Write Test Specification
  3. Define Verifiable Tests
  4. Execute Tests via Subagents
  5. Fix Failures (Optional)

What it can do on your machine

Read from SKILL.md and the folder at commit 2bf50c9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Integration Testing loads about 908 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 384 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~908

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 384 words (~908 tokens).

“This skill guides the creation and autonomous execution of verifiable integration test specifications. It ensures that tests are actionable by agents, properly documented, and systematically executed by subagents to validate features or fix failures.”

— opening of SKILL.md by av
name
agent-integration-testing

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .agents/skills/agent-integration-testing of av/mi.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit 2bf50c9

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in av/mi, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Integration Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Integration Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Integration Testing this skillav/mi102—~908Automated safety check: PassNone
Automate Integration Testopenshift/oc-mirror124—~862Automated safety check: PassApache-2.0
Migrate E2E To Integrationopenshift/oc-mirror124—~1.5kAutomated safety check: PassApache-2.0
Poweruser Feature Auditpydantic/pydantic-ai20k—~2.9kAutomated safety check: PassMIT
Write Frontend TestsElite588/AUTOGPT103—~1.9kAutomated safety check: PassCustom licence
API Test Suite Builderalirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Automate Integration Test

    openshift/oc-mirror

    Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror

    124 GitHub stars~862 tokensUpdated today
    Testing & QAAuto-check passed
  • Migrate E2E To Integration

    openshift/oc-mirror

    Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns

    124 GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed
  • Poweruser Feature Audit

    pydantic/pydantic-ai

    Official

    Independent power-user audit of a big new-feature PR. An agent skill from pydantic/pydantic-ai.

    20k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Write Frontend Tests

    Elite588/AUTOGPT

    Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them.

    103 GitHub stars~1.9k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • API Test Suite Builder

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    Testing & QAAuto-check passed
  • Atmos Tests

    cloudposse/atmos

    Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…

    1.4k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Anneal

    av/mi

    A skill your agent uses when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other…

    102 GitHub stars~3.8k tokensUpdated 11 days ago
    Auto-check passed
  • Scans a codebase to tag every fact as draft, spec or implemented based on what the code actually shows, adding missing facts and fixing or removing wrong ones.

    102 GitHub stars~2.8k tokensUpdated 11 days ago
    Auto-check passed
  • Implements every @spec fact from a project's fact sheet in code, tags each one @implemented once done, and reports exactly what is left if it cannot finish.

    102 GitHub stars~1.3k tokensUpdated 11 days ago
    Auto-check passed
  • Works with you to turn draft behavioral facts into precise, implementable spec facts, resolving vague labels, gaps and contradictions one at a time through discussion.

    102 GitHub stars~1.5k tokensUpdated 11 days ago
    Auto-check passed
  • Ideate

    av/mi

    Timeboxed ideation on a topic using propose-and-critique subagent pairs.

    102 GitHub stars~2.8k tokensUpdated 11 days ago
    Auto-check passed
  • Self

    av/mi

    Answer questions about how 'mi' works, write new tools, or modify the harness.

    102 GitHub stars~1.4k tokensUpdated 11 days ago
    Auto-check passed

Categories

Questions about Agent Integration Testing

What does Agent Integration Testing do?

Writes plain-English integration test specs with verifiable steps and expectations, then runs each one through a subagent that reports pass or fail with logs. md with a Prerequisites section listing any setup needed, such as environment variables, database seeding or background services. Each test is written in plain English with clear reproduction steps and a set of expectations, and every expectation must be strictly verifiable by an agent using tools such as shell commands, HTTP requests or file reads; an expectation that cannot be checked this way is invalid and has to be rewritten or removed.

When should I use Agent Integration Testing?

Agent Integration Testing fits situations like: writing an integration test plan for a feature before validating it; running integration tests through subagents and collecting pass or fail results; fixing failures found during an integration test run.

How do I install Agent Integration Testing in Claude Code?

Run `npx skills add av/mi --skill agent-integration-testing -a claude-code`. Or copy the skill folder (.agents/skills/agent-integration-testing in av/mi) into .claude/skills/agent-integration-testing in your project. Claude Code loads it when a task matches its description.

How do I install Agent Integration Testing in Codex?

Run `npx skills add av/mi --skill agent-integration-testing -a codex`. Or copy the skill folder (.agents/skills/agent-integration-testing in av/mi) into .agents/skills/agent-integration-testing in your project. Codex loads it when a task matches its description.

Can I use Agent Integration Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add av/mi --skill agent-integration-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-integration-testing, .gemini/skills/agent-integration-testing, .github/skills/agent-integration-testing and .opencode/skills/agent-integration-testing in your project.

What does Agent Integration Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Integration Testing is instructions for the agent only.

Does Agent Integration Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Integration Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Integration Testing use?

No licence was found for Agent Integration Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Agent Integration Testing use?

About 908 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Integration Testing?

Skills that share tags, products or a category with Agent Integration Testing: Automate Integration Test (openshift/oc-mirror, 124 stars), Migrate E2E To Integration (openshift/oc-mirror, 124 stars), Poweruser Feature Audit (pydantic/pydantic-ai, 20k stars) and Write Frontend Tests (Elite588/AUTOGPT, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Integration Testing?

av (a GitHub user) maintains it in av/mi, which has 102 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 26, 2026.

Source: av/mi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.