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 bricerising/enterprise-software-playbook --skill testinggit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/testing)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/testing"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/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/bricerising/enterprise-software-playbook/testing"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/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.00073 | $0.01279 |
| Opus 5.5 | $0.00029 | $0.00512 |
| Sonnet 5.5 | $0.00015 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing (Consumer Test Coverage)
Overview
Improve coverage by exercising consumer-visible behavior with infra mocked and behavior preserved.
Inputs / Outputs
Inputs: Spec/contract artifacts from spec or plan (optional but preferred); consumer-facing entrypoints to test.
Outputs: Test suite pinning consumer-visible behavior; coverage report. Consumed by finish and review.
Workflow
- Read relevant specs (system + service) and map them to consumer-visible flows and invariants.
- Identify consumer-facing entrypoints: HTTP/gRPC handlers, public service methods, event consumers, cache/storage adapters, jobs.
GATE: Do not write tests until consumer-facing entrypoints are identified (step 2). If no entrypoints are listed, go back — tests without identified entrypoints tend to test implementation details.
- Add tests for success and failure paths that a consumer can observe (invalid input, downstream failures, permissions, timeouts where applicable).
- Mock infra boundaries (DB, Redis, network listeners, clocks/timers). Prefer calling handlers/functions directly instead of running real servers.
- Run focused coverage and iterate until the target is met (default 80% unless the spec says otherwise).
Minimum viable execution
When context or time is constrained, these are the load-bearing steps:
- Read specs and map to consumer-visible flows (step 1) — tests must trace back to spec'd behavior.
- Identify consumer-facing entrypoints (step 2) — determines what to test.
- Write success + failure path tests (step 3) — both paths, not just happy path.
- Run coverage (step 5) — verify the tests actually exercise the code.
Steps that can be cut under pressure: mocking strategy optimization (step 4), coverage iteration beyond first pass.
Chooser (What Test Type Where)
- New endpoint / handler change: consumer-visible tests — call handler with mocked dependencies, assert response shape + status codes + error handling.
- Refactor (no behavior change): characterization tests first — pin existing behavior before changing implementation.
- New event consumer / job: feed mixed payloads (valid, invalid, missing fields, duplicates); assert side effects and idempotency.
- Boundary change (DB/cache/client): adapter tests — cover happy path, empty/null results, connection failures, timeouts.
- Cross-service contract change: consumer-contract tests — verify your consumer expectations match the provider's contract.
- Coverage gap (existing code): start with the riskiest paths — auth/permissions, error handling, input validation, state transitions.
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.
- 1mo ago First seen · 98 lines · 73 tokens per session scan A 268d23aa806f
testing is a skill published in the GitHub repository bricerising/enterprise-software-playbook (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,279 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
test-and-fix
Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.
nemo-automodel-model-onboarding
Guide for onboarding new model architectures into NeMo AutoModel, including architecture discovery, implementation patterns, registration, and validation.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.