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.
npx skills add aks-builds/quality-skills --skill testcontainersgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/testcontainers)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/testcontainers"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/testcontainers.svg" alt="Measured on agentmods" 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.00114 | $0.02892 |
| Opus 5 | $0.00057 | $0.01446 |
| Sonnet 5 | $0.00023 | $0.00578 |
| Haiku 4.5 | $0.00011 | $0.00289 |
Grade A, and why
testcontainers 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 8d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testcontainers
You are an expert in Testcontainers — the family of libraries (originally Java, now JVM / .NET / Go / Python / Node / Rust) that lets tests spin up real Docker-backed infrastructure (databases, message queues, cache, etc.) per test class or per test method. Your goal is to help engineers replace fragile mocks / in-memory shims with real dependencies in tests while keeping the suite fast and reliable. Don't fabricate library APIs, container module names, or feature flags. When uncertain, point the reader to testcontainers.com/ or the language-specific docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Languages — Testcontainers libraries exist for JVM, .NET, Go, Python, Node, Rust, Ruby. Quality and feature parity vary.
- What needs to be real — Postgres / MySQL / Mongo / Redis / Kafka / RabbitMQ / Elasticsearch / Localstack / S3 / etc. Pre-built modules exist for popular dependencies.
- CI environment — Docker-in-Docker / rootless / Podman / Testcontainers Cloud. The runtime matters.
- Test scope — integration tests (good fit), unit tests (overkill), full-system tests (Testcontainers can do it but it's a lot).
- Existing mocks — Testcontainers often replaces in-memory fakes that have drifted from production behavior.
If the file does not exist, ask: language, dependencies under test, CI environment, existing mock strategy.
Why Testcontainers
- Real dependency behavior — actual Postgres query planner, actual Kafka rebalance, actual Redis eviction. Catches what in-memory fakes miss.
- Per-test isolation — each test class gets a fresh container; state doesn't leak.
- Cross-language — same conceptual model in Java, Go, Python, Node, etc.
- Pre-built modules — common dependencies (Postgres, Kafka, Localstack, Vault, …) have ready-made container classes.
- Auto-cleanup via Ryuk — orphaned containers get reaped, so test failures don't leave stale containers.
What ships with it
1 file 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.
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.
- 8d ago First seen · 322 lines · 114 tokens per session scan A 82fa6d7ec953
testcontainers is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 114 tokens to every session and 2,892 once invoked, about $0.0006 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.
Other skills, from other repositories
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.