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 martian56/claude-engineer --skill testing-and-qualitygit clone --depth 1 https://github.com/martian56/claude-engineerWrote 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/martian56/claude-engineer/testing-and-quality)<a href="https://agentmods.dev/skills/martian56/claude-engineer/testing-and-quality"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/testing-and-quality.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.00058 | $0.00666 |
| Opus 5 | $0.00029 | $0.00333 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
testing-and-quality 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing & Quality
Announce at start: "I'm using claude-engineer:testing-and-quality to enforce the four quality gates."
Iron Law
No "done" without all four gates passing, verified by fresh evidence. (Pairs with
superpowers:verification-before-completion - assertions follow evidence, never precede it.)
The four gates (exact pass/fail commands; exit 0 = pass)
- Tests + coverage - FE
vitest run --coverage; BEpytest --cov=app --cov-fail-under=80. - E2E + zero console errors -
playwright test(specs include a console-error/pageerrorfixture and assert no 4xx/5xx on key routes). Drive flows and confirm every button/screen works via the Playwright + Chrome DevTools MCPs. - Accessibility (WCAG AA) -
playwright test a11y/using@axe-core/playwrightwith tagswcag2a,wcag2aa,wcag21aa,wcag22aa; assert zero violations. Manual keyboard/focus spot-checks too. - Strict types + lint clean -
tsc --noEmit && eslint . && prettier --check . && ruff check . && ruff format --check . && mypy app.
The gate runner + commit gate
- Scaffold
scripts/quality-gate.mjsfromtemplates/quality-gate.mjs. It runs all four gates and writes.claude-engineer/quality-gate-status.json({ allPass, results }). - The claude-engineer PreToolUse(Bash) hook blocks
git commitunless that file showsallPass: true. So: runnode scripts/quality-gate.mjs→ fix failures → commit. Intentional bypass:git commit --no-verify. - The same four commands are the finish condition and the CI merge condition (
claude-engineer:ci-cd-pipeline).
Browser verification (MCPs - BYO install)
- Chrome DevTools MCP - capture/assert zero console errors per screen, Lighthouse audits, network-failure checks.
- Playwright MCP - drive real flows; confirm interactions actually work.
Install per
templates/recommended-mcps.md.
Full detail (test pyramid, coverage targets, Playwright setup, the console-error fixture, axe usage, exact commands):
read references/testing-and-gates.md on demand.
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 · 39 lines · 58 tokens per session scan A fb79160ba6d4
testing-and-quality is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 666 once invoked, about $0.0003 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
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked…
playwright-harness
Drive a real browser with Playwright on any OS and gate on what you observe: write a script, launch Chromium (headless by default; a shared headed window when a human must watch or drive), drive the page, and assert on screenshots plus collected page errors. The operational trunk for browser work; specializations…
playwright-storybook-flows
Specialization of playwright-harness for AUTHORING and REPRODUCING flows. A flow is a sequence of steps a human or an agent can take inside an application to demonstrate a specific feature; it is written as a Storybook docs page in a conventional location, where a human reads it as a manual walkthrough (issue…
test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
android-emulator-mask-testing
Specialization of android-emulator-harness for CAMERA / segmentation testing: get a real PERSON in front of the emulator camera so MediaPipe / ML Kit selfie segmentation produces an actual mask, then verify background-replacement / blur / shader effects and tune mask threshold by vision. Use when the task is "test the…
playwright-camera-mask-testing
Specialization of playwright-harness for CAMERA / segmentation testing in the browser: put a real PERSON in front of getUserMedia so MediaPipe / selfie segmentation produces an actual mask, then verify background-replacement / blur / shader effects by vision. Use when the task is "test the mask on web", "verify…