Mythic-MCP: Skill for Claude Code

.claude/skills/integration-test-planning/SKILL.md

integration-test-planning is a skill for Claude Code from nbaertsch/Mythic-MCP. It costs 59 tokens per session (5,394 once invoked), scanned A, original, MIT.

A guide for planning integration and end-to-end tests using real services, test data, and Docker. Integration tests check connections between parts of a system; end-to-end tests check a complete user workflow.

In plain words
What is it for?
Use it to plan test coverage, set up test environments, manage test data, validate service integrations, and investigate test failures.
Why use it?
It helps test real data flows and service boundaries instead of relying mainly on simulated components.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is nbaertsch/Mythic-MCP's own configuration. It tells Claude Code how to work on Mythic-MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Mythic-MCP configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is - ./tests/mocks:/config.

Reuse

Borrowing it

Nothing to install: this file belongs to nbaertsch/Mythic-MCP. 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/nbaertsch/Mythic-MCP/main/.claude/skills/integration-test-planning/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nbaertsch/Mythic-MCP

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.

agentmods badge for integration-test-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/nbaertsch/mythic-mcp/integration-test-planning/github.svg)](https://agentmods.dev/skills/nbaertsch/mythic-mcp/integration-test-planning)
Your own site
<a href="https://agentmods.dev/skills/nbaertsch/mythic-mcp/integration-test-planning"><img src="https://agentmods.dev/badge/skills/nbaertsch/mythic-mcp/integration-test-planning/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.

agentmods 80×15 button for integration-test-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/nbaertsch/mythic-mcp/integration-test-planning"><img src="https://agentmods.dev/badge/skills/nbaertsch/mythic-mcp/integration-test-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,394 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00059 $0.05394
Opus 5 $0.00030 $0.02697
Sonnet 5 $0.00012 $0.01079
Haiku 4.5 $0.00006 $0.00539

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

Security

Grade A, and why

integration-test-planning 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 9d ago.

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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

subprocess.run(['docker-compose', '-f', 'docker-compose.test.yml', 'up', '-d'])
.claude/skills/integration-test-planning/SKILL.md · 773 lines

How it starts

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

Integration Test Planning

Comprehensive guide for designing and implementing integration and end-to-end tests that validate real system behavior.

When to Use This Skill

Invoke this skill when:

  • Planning test strategy for a feature
  • Implementing integration tests
  • Setting up test environments
  • Designing test data management
  • Troubleshooting test failures
  • Validating service integrations
  • Ensuring test coverage

Test Strategy Framework

Test Level Definitions

Integration Tests:

  • Test interactions between 2+ services/components
  • Use real databases, APIs, caches
  • Validate data flows across boundaries
  • Test service contracts and interfaces
  • Shorter than E2E, focused on subsystems

End-to-End Tests:

  • Test complete user workflows
  • Involve all system components
  • Validate full stack integration
  • Test from entry point to data persistence
  • Realistic user scenarios

Unit Tests (Minimal in CI-First):

  • Only for complex business logic
  • Algorithms, calculations, transformations
  • NOT for database queries, API calls, or integrations
  • Should be a small portion of total tests

Test Environment Setup

Docker Compose for Real Services

Example: Web Application Test Environment

# docker-compose.test.yml
version: '3.8'

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile.test
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_started
    environment:
      NODE_ENV: test
      DATABASE_URL: postgresql://testuser:testpass@postgres:5432/testdb
      REDIS_URL: redis://redis:6379/0
      JWT_SECRET: test-secret-key
      API_PORT: 3000
    ports:
      - "3000:3000"

  postgres:
    image: postgres:15-alpine
    environment:
      POSTGRES_USER: testuser
      POSTGRES_PASSWORD: testpass
      POSTGRES_DB: testdb
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U testuser"]
      interval: 5s
      timeout: 5s
      retries: 5
    tmpfs:
      - /var/lib/postgresql/data  # Fast in-memory storage for tests

  redis:
    image: redis:7-alpine
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 5s
      timeout: 3s
      retries: 5

  # Optional: External API mock
  mock-api:
    image: mockserver/mockserver:latest
    environment:
      MOCKSERVER_INITIALIZATION_JSON_PATH: /config/expectations.json
    volumes:
      - ./tests/mocks:/config

Read the full file on GitHub · 773 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. 9d ago First seen · 773 lines · 59 tokens per session scan A f8ff8dc98a58

Subscribe to this mod's changes

integration-test-planning is a skill published in the GitHub repository nbaertsch/Mythic-MCP (6 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 5,394 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog-foss · 112 tokens

pyats-dynamic-test

Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.

automateyournetwork/netclaw · 61 tokens

test-loop

Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).

HoangNguyen0403/agent-skills-standard · 25 tokens

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens