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/elct9620/ai-coding-skills/testingnpx skills add elct9620/ai-coding-skills --skill testinggit clone --depth 1 https://github.com/elct9620/ai-coding-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/elct9620/ai-coding-skills/testing)<a href="https://agentmods.dev/skills/elct9620/ai-coding-skills/testing"><img src="https://agentmods.dev/badge/skills/elct9620/ai-coding-skills/testing.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 | $0.00102 | $0.03728 |
| Opus 5 | $0.00051 | $0.01864 |
| Sonnet 5 | $0.00020 | $0.00746 |
| Haiku 4.5 | $0.00010 | $0.00373 |
Grade A, and why
testing 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 3d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Related Skills
- Found a code smell while writing tests? → Use refactoring to fix it first
- Need to design the class structure before testing? → Use design-patterns or principles
- Adding a database migration or API endpoint? → Use schema alongside testing
Applicability Rubric
| Condition | Pass | Fail |
|---|---|---|
| New feature implementation | Adding new functionality | No new behavior |
| Behavior change | Modifying existing behavior | No behavior change |
| Bug fix | Fixing a defect | Non-bug change |
| Pre-refactoring | Ensuring tests exist before refactor | Tests already sufficient |
Apply when: Any condition passes
Core Principles
Integration-First Philosophy
Ensure components work together first, then verify individual component details. Unit tests are supplementary — only add them for edge cases that integration tests cannot practically cover.
| Scenario | Action |
|---|---|
| Starting new feature | Write integration/E2E test first |
| Integration test passes | Add unit tests only for uncovered edge cases |
| Edge case not covered by integration | Add unit test for specific case |
| Component works alone but fails together | Missing integration test coverage |
| Module has no integration test path | Verify the module serves a real user need; if it does, add the missing integration path |
Proving the Net Holds
A suite running green proves the code passes the tests, not that the tests would notice if the code broke. Where the same hand wrote the code, wrote the tests, and reports the result, green is self-issued and carries no more weight than the claim itself.
What settles it is breaking the code on purpose and watching a test object. Take a promise the spec makes about the scope, change the code so that promise is violated — 410 becomes 404, a guard disappears, a boundary moves one step — then run the suite.
| Baseline | With the break in | After restoring | Reading |
|---|---|---|---|
| Green | Red | Diff matches | The net holds for that promise |
| Green | Green | Diff matches | Nothing was watching — the missing test is the finding |
| Red | — | — | Nothing follows; the baseline has to be green first |
| Green | Red | Diff differs | Restoration failed — the tree is dirty, stop and say so |
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.
- 3d ago First seen · 300 lines · 102 tokens per session scan A 18253c84efa4
testing is a skill published in the GitHub repository elct9620/ai-coding-skills (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,728 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
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
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.
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求.
prd-auto-test-loop
PRD 驱动的自动化测试编排技能。用于把每版 PRD 的测试计划、AI 自测与自修复、测试报告标准化落地；适用于按验收标准拆分 Unit/Integration/E2E、划分自动化与人工边界、生成版本化 TESTPLAN/TESTREPORT 的场景。.