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 thixpin/pitway --skill testinggit clone --depth 1 https://github.com/thixpin/pitwayWrote 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/thixpin/pitway/testing)<a href="https://agentmods.dev/skills/thixpin/pitway/testing"><img src="https://agentmods.dev/badge/skills/thixpin/pitway/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/thixpin/pitway/testing"><img src="https://agentmods.dev/badge/skills/thixpin/pitway/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.00085 | $0.00741 |
| Opus 5.5 | $0.00034 | $0.00296 |
| Sonnet 5.5 | $0.00017 | $0.00148 |
| Haiku 4.5 | $0.00009 | $0.00074 |
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Write tests that fail for exactly one reason, pass deterministically, and survive refactoring.
Scope
Use for deciding what to test and writing it: new tests, coverage gaps, flaky tests, test structure, setting up a suite.
Do not use for:
- Diagnosing why production code misbehaves when the cause is unknown — use
debugging. Once the cause is identified,bug-fixreturns here for the regression test. - Judging non-test production code — use
code-quality-review.
What to test
- Test observable behavior and contracts, not implementation details. A refactor that preserves behavior should not break tests.
- Prioritize by risk: core business logic and boundary conditions first, then error paths, then integration seams. Do not chase coverage numbers for trivial code (getters, framework glue).
- Every bug fix gets a regression test (see the
bug-fixskill). - Follow the project's existing test framework, directory layout, naming, and assertion style — do not introduce a new test framework into a project that has one.
Determinism
- No hidden dependencies on wall-clock time, timezones, locale, random seeds, network, or test execution order. Inject clocks, seed randomness, and fake external services at the boundary.
- Each test owns its setup and teardown; tests must pass in isolation and in any order.
- Treat flaky tests as defects in the test suite: find the nondeterminism instead of masking it with retries or sleeps. If the nondeterminism turns out to be in the production code rather than the test, hand off to
debugging.
Databases and external state
- Never test against a development, staging, or production database. Use the project's test database, or add a disposable one (container or in-process instance) if none exists.
- Assert in global setup that the target is the test database; never let a missing test configuration fall back to the default database.
- Reset between tests — transaction rollback, truncation, or a fresh schema. Never rely on data left by another test or manual seeding.
- Never share a test database between parallel test runs unless the project explicitly supports it.
- Apply the same isolation rules to caches, queues, object storage, and search indexes — use isolated instances or per-test namespaces.
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 · 53 lines · 85 tokens per session scan A b71ae5e9bcf6
testing is a skill published in the GitHub repository thixpin/pitway (20 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 741 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-30.
Other skills, from other repositories
systematic-debugging
Structured root-cause debugging loop — reproduce, isolate, form a hypothesis, verify the fix. Use whenever a bug, crash, test failure, or unexpected behavior is reported.
fix-issue
Fix a GitHub issue following project coding standards. Creates branch, implements fix with TDD, and prepares PR.
systematic-debugging
Reproduce failures, isolate root cause with evidence, and fix them through a regression test.
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.