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 pnakhat/qa-ai-repo --skill test-pyramidgit clone --depth 1 https://github.com/pnakhat/qa-ai-repoWrote 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/pnakhat/qa-ai-repo/test-pyramid)<a href="https://agentmods.dev/skills/pnakhat/qa-ai-repo/test-pyramid"><img src="https://agentmods.dev/badge/skills/pnakhat/qa-ai-repo/test-pyramid/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/pnakhat/qa-ai-repo/test-pyramid"><img src="https://agentmods.dev/badge/skills/pnakhat/qa-ai-repo/test-pyramid.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.00100 | $0.01936 |
| Opus 5 | $0.00050 | $0.00968 |
| Sonnet 5 | $0.00020 | $0.00387 |
| Haiku 4.5 | $0.00010 | $0.00194 |
Grade A, and why
test-pyramid 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 11d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full-Stack Test Pyramid
Design testing for an application as a whole system of layers, not one suite.
The goal: every behavior is tested at the lowest level that can meaningfully
verify it, seams are covered by contract tests, and only a handful of
journeys reach end-to-end. See layer-test-matrix.md for the full
layer × level grid of what to test and which tools to use, and reference.md
for a runnable example test at every level (plus a "push a test down" before/after).
Method
-
Map the architecture. Identify each layer and its technology:
- Frontend — SPA/SSR framework, state management, design system, routes.
- Backend — services, APIs (REST/GraphQL/gRPC), domain logic, data stores.
- Middleware — API gateway/BFF, auth, message queues/event bus, caching,
service mesh, background workers, third-party integrations.
Inspect the repo (package manifests, framework configs,
src/layout, CI) and confirm rather than assume.
-
List behaviors per layer, then assign each to the lowest suitable level using this decision order:
- Pure logic / rendering / validation → unit.
- Behavior that needs a real collaborator (DB, rendered tree + network, queue) → integration / component.
- Agreement across a boundary (FE↔API, service↔service, producer↔consumer) → contract (Pact / OpenAPI / AsyncAPI) — this is what lets you keep E2E small.
- Only a full critical user journey that no lower level can prove → E2E.
-
Cover the seams, not the internals twice. Where two layers meet, use a contract test once instead of re-testing both sides through E2E.
-
Set the shape. Aim for a true pyramid, roughly:
- ~70% unit · ~20% integration/component · <10% contract+E2E (E2E a small handful). If the current suite is an inverted "ice-cream cone" (mostly E2E), call it out and give the rebalancing plan.
-
Output the plan using
plan-template.md: per-layer test lists, the seam contracts, the few E2E journeys, target proportions, tooling, CI wiring, and what to build first.
What ships with it
3 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.
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.
- 11d ago First seen · 121 lines · 100 tokens per session scan A d5ea0efb4159
test-pyramid is a skill published in the GitHub repository pnakhat/qa-ai-repo (2 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 1,936 once invoked, about $0.0005 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
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…