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.
curl -O https://raw.githubusercontent.com/nbaertsch/Mythic-MCP/main/.claude/skills/integration-test-planning/SKILL.mdgit clone --depth 1 https://github.com/nbaertsch/Mythic-MCPWrote 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.
[](https://agentmods.dev/skills/nbaertsch/mythic-mcp/integration-test-planning)<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.
<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>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.00059 | $0.05394 |
| Opus 5.5 | $0.00024 | $0.02158 |
| Sonnet 5.5 | $0.00012 | $0.01079 |
| Haiku 4.5 | $0.00006 | $0.00539 |
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 2mo 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']) 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
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.
- 2mo ago First seen · 773 lines · 59 tokens per session scan A f8ff8dc98a58
integration-test-planning is a skill published in the GitHub repository nbaertsch/Mythic-MCP (10 stars, last pushed 8mo ago), licensed MIT. It adds 59 tokens to every session and 5,394 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.