test-environments

test-environments is a skill for Claude Code, Codex from petrkindlmann/qa-skills. It costs 157 tokens per session (4,326 once invoked), scanned A, original, MIT.

A guide for planning test environments across local development, continuous integration, previews, staging, and production.

In plain words
What is it for?
Use it to design Docker Compose testing, multi-stage Dockerfiles, seed-data processes, per-change preview environments, production matching, and HTTP stubs for external services.
Why use it?
It helps prevent bugs caused by differences in databases, services, test data, containers, or third-party APIs between environments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design Docker Compose testing, multi-stage Dockerfiles, seed-data processes, per-change preview environments, production matching, and HTTP stubs for external services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/petrkindlmann/qa-skills/test-environments
Install

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.

Any agent
npx skills add petrkindlmann/qa-skills --skill test-environments
Clone the repo
git clone --depth 1 https://github.com/petrkindlmann/qa-skills

Made for: Claude Code, Codex.

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 test-environments

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/test-environments"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/test-environments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 157 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,326 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. Third-party audits
  • Socket pass 11 May 2026
  • Snyk warn 11 May 2026
How audits are shown
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.00157 $0.04326
Opus 5 $0.00078 $0.02163
Sonnet 5 $0.00031 $0.00865
Haiku 4.5 $0.00016 $0.00433

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

Security

Grade A, and why

test-environments 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf https://staging.example.com/health || exit 1
skills/test-environments/SKILL.md · 375 lines

How it starts

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

Discovery Questions

Check .agents/qa-project-context.md first — if it exists, use it and skip anything already answered there. Then:

  1. How many environments exist today? Local dev, CI, staging, preview, production? Map what you have before designing what you need.
  2. Is the app containerized? Check for Dockerfile, docker-compose.yml, or compose.yaml. If yes, multi-stage targets and compose come for free; if not, that is the first deliverable.
  3. How is test data seeded? Manual SQL, migration-based, factory libraries, or production snapshots? This decides whether seed scripts are a quick win or a rewrite.
  4. How close is staging to production? Same DB engine, queue, cache, auth provider, orchestration? Each mismatch is a class of bugs staging can never catch.
  5. External dependencies: How many third-party APIs does the system call, and are they stubbed in non-prod? Unstubbed third parties are the top source of CI flake.

Core Principles

1. Staging must mirror production where bugs hide. If staging uses SQLite and production uses PostgreSQL, staging tests prove nothing about prod behavior. Match the database engine and version, the queue system, the cache layer, and the auth provider — those are where environment-specific bugs live.

2. Ephemeral environments beat long-lived ones. A shared staging environment becomes a bottleneck where one broken deploy blocks the entire team. Per-PR preview environments give isolation and parallel testing; keep staging only for final pre-release validation.

Read the full file on GitHub · 375 lines

Files

What ships with it

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

  1. 9d ago First seen · 375 lines · 157 tokens per session scan A 6559533f36de

Subscribe to this mod's changes

test-environments is a skill published in the GitHub repository petrkindlmann/qa-skills (114 stars, last pushed 3mo ago), licensed MIT. It adds 157 tokens to every session and 4,326 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.