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 zircote-plugins/sdlc-quality --skill testinggit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/zircote-plugins/sdlc-quality/testing)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/testing"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/testing/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/zircote-plugins/sdlc-quality/testing"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/testing.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.00068 | $0.01354 |
| Opus 5.5 | $0.00027 | $0.00542 |
| Sonnet 5.5 | $0.00014 | $0.00271 |
| Haiku 4.5 | $0.00007 | $0.00135 |
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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards
Guidance for implementing comprehensive testing that meets SDLC requirements.
Tooling
Available Tools: If using Claude Code, the
pr-review-toolkit:pr-test-analyzeragent reviews test coverage and identifies gaps. Use after creating PRs to ensure adequate test coverage.
Test Organization
Required Test Categories (MUST)
Projects MUST maintain these test categories:
| Category | Location | Purpose |
|---|---|---|
| Unit tests | Alongside source code | Test individual functions/methods |
| Integration tests | Dedicated test directory | Test component interactions |
| Documentation tests | Within doc comments | Verify examples work |
| End-to-end tests | Dedicated e2e directory | Test full system behavior |
Naming Convention (MUST)
Test files MUST be clearly identifiable by naming convention:
| Language | Unit Tests | Integration Tests |
|---|---|---|
| Rust | mod tests in source |
tests/ directory |
| TypeScript | *.test.ts, *.spec.ts |
tests/integration/ |
| Python | test_*.py, *_test.py |
tests/integration/ |
| Java | *Test.java |
*IntegrationTest.java |
| Go | *_test.go |
*_integration_test.go |
Test Coverage
Coverage Requirements
| Requirement | Level |
|---|---|
| New functionality | MUST include tests |
| Bug fixes | MUST include regression tests |
| Coverage measurement | MUST be tracked |
| Minimum coverage | SHOULD target 80% |
| Critical paths | MUST have 95%+ coverage |
| Coverage reports | MUST be uploaded to tracking service |
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.
- 1mo ago First seen · 204 lines · 68 tokens per session scan A 77796845e16d
testing is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 29d ago), licensed MIT. It adds 68 tokens to every session and 1,354 once invoked, about $0.0003 per session on Opus 5.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
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
cao-contributing
Contribute changes to the CAO (CLI Agent Orchestrator) codebase — the local dev loop, the CI gate map, and the pre-PR checklist. Use when the user says "open a PR", "why did CI fail", "run the checks before I push", "the mypy/Code Quality job is red", "add a test and verify coverage", or when making any code change…
specflow
Spec-driven development with executable contracts.
specflow-simulate
Simulates end-to-end usage of a Specflow story across multiple personas and divergent routes to discover gaps, edge cases, and unhandled branches BEFORE the story is built — then proposes each finding as a concrete story addition (new REQ, negative-path AC, Gherkin branch, or journey step). This is the high-value…
ci-pipeline-and-gates
Enforces a lean GitHub Actions Flutter CI where every gate maps to one named release-blocking contract — pinned runner + subosito/flutter-action@v2 toolchain, dart format --set-exit-if-changed, flutter analyze --fatal-infos, buildrunner and drift schema freshness (git diff --exit-code), flutter test…