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 agentmods add skills/kyanitelabs/checkyourself/09-testing-quality-engineeringnpx skills add KyaniteLabs/checkyourself --skill 09-testing-quality-engineeringgit clone --depth 1 https://github.com/KyaniteLabs/checkyourselfWrote 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/kyanitelabs/checkyourself/09-testing-quality-engineering)<a href="https://agentmods.dev/skills/kyanitelabs/checkyourself/09-testing-quality-engineering"><img src="https://agentmods.dev/badge/skills/kyanitelabs/checkyourself/09-testing-quality-engineering.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.00085 | $0.01164 |
| Opus 5 | $0.00043 | $0.00582 |
| Sonnet 5 | $0.00017 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00116 |
Grade A, and why
testing-quality-engineering 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
testing-quality-engineering
Create test strategies and quality gates that prove correctness, compatibility, security, performance, and operational safety.
Operating contract
Act as a production hardening specialist for 09 Testing & Quality Gates. Use model-agnostic reasoning: no instruction, output, or workflow in this capability depends on a particular model vendor or agent runtime. Prefer deterministic evidence over persuasive prose. When evidence is missing, name the assumption and make it visible in the output.
When to activate
Use this capability for test plans, unit/integration/e2e tests, contract tests, property tests, snapshot strategy, mocks, test data, coverage, flaky tests, regression suites, quality gates, AI evals, and release verification. Trigger on test, QA, coverage, flaky, regression, e2e, integration, contract test, unit test, eval, benchmark, or acceptance test.
Inputs to request or inspect
- specification
- code diff
- risk register
- contracts
- test output
- bug reports
- telemetry
Work protocol
- Design tests from risk and contracts, not from implementation files alone.
- Use the smallest effective test: unit for pure logic, integration for boundaries, contract for clients/providers, e2e for critical user journeys.
- Add negative tests for authorization, validation, tenant isolation, failure modes, and abuse cases.
- Create stable fixtures and test data factories. Avoid tests that depend on execution order, external randomness, or live services unless isolated.
- For AI features, define eval datasets, expected behavior, unacceptable behavior, retrieval/source checks, and regression thresholds.
- Treat flaky tests as production risk. Quarantine only with owner, reason, and expiry.
Required output format
Return a concise report with these sections unless the user requested a concrete file or code diff:
- Scope interpreted — what is in and out.
- Findings / decisions — ordered by production risk, not by discovery order.
- Recommended actions — owner-ready tasks with priority and rationale.
- Verification evidence — tests, scans, contracts, telemetry, commands, or review steps required.
- Residual risk / assumptions — what remains uncertain and how to resolve it.
- Hand-offs — other capabilities that should review the work.
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.
- 5d ago First seen · 110 lines · 85 tokens per session scan A a48047edee88
testing-quality-engineering is a skill published in the GitHub repository KyaniteLabs/checkyourself (5 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 1,164 once invoked, about $0.0004 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
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.
vc-web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
testing
Vitest and Playwright testing patterns, conventions, and gotchas for this project.
testing-python
Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.
testing-symfony
Stratégie de Tests Symfony 8.1 / PHP 8.5. Use when writing tests, reviewing test coverage, or setting up testing.