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 nweii/agent-stuff --skill software-test-qualitygit clone --depth 1 https://github.com/nweii/agent-stuffWrote 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/nweii/agent-stuff/software-test-quality)<a href="https://agentmods.dev/skills/nweii/agent-stuff/software-test-quality"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/software-test-quality/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/nweii/agent-stuff/software-test-quality"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/software-test-quality.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.00037 | $0.00712 |
| Opus 5.5 | $0.00015 | $0.00285 |
| Sonnet 5.5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
software-test-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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software test quality
Choose the branch that matches the task:
- Existing tests or suite → Review test quality
- Proposed behavior or risk → Choose the test level
- Recent changes with missing regression protection → Read coverage-gaps.md
When building a feature or fixing a bug test-first, use an available tdd skill or the repository’s equivalent test-first procedure. This skill needs access to the code, test conventions, and runnable checks for implementation work; supplied tests are enough for a review.
Review test quality
Review tests through their public seam: the interface where callers observe behavior. A test should fail when that behavior breaks and survive internal refactors that preserve it.
Apply the Desiderata as design lenses, not a checklist:
- Isolated: results do not depend on execution order or shared mutable state.
- Composable: tests combine without hidden coupling or cascading setup.
- Deterministic: unchanged code and inputs produce the same result.
- Fast: tests are quick enough to run while working.
- Writable: creation cost is proportionate to the behavior protected.
- Readable: motivation and expected behavior are clear.
- Behavioral: the result changes when the behavior changes.
- Structure-insensitive: internal refactors do not change the result.
- Automated: tests run without manual intervention.
- Specific: failures make the likely cause clear.
- Predictive: passing gives justified confidence in production behavior.
- Inspiring: the suite increases confidence instead of creating noise, flakes, or avoidance.
Then inspect the failure modes that a structural review can miss:
- Weak assertions that prove existence instead of behavior.
- Fixtures that do not represent production inputs.
- Risky paths that the suite never exercises.
- Names that disagree with the behavior asserted.
- Mocks that encode assumptions the real collaborator does not satisfy.
- Tautological expectations derived through the same logic as the implementation.
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 Changed · +1 lines · -17 tokens per session eaedeb4d6a08
- 1mo ago First seen · 61 lines · 54 tokens per session scan A 9422a37b11a0
software-test-quality is a skill published in the GitHub repository nweii/agent-stuff (10 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 712 once invoked, about $0.0001 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
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.
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.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.