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/amanktyr/tailor/testingnpx skills add AmanKtyr/Tailor --skill testinggit clone --depth 1 https://github.com/AmanKtyr/TailorWhat 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.00023 | $0.00598 |
| Opus 5 | $0.00012 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Discipline Skill
Activate this skill when creating features, fixing bugs, refactoring code, or running verification test suites.
Testing Law: Untested code is broken code. Verified code has exit code 0.
1. Targeted Test Execution Matrix
Run targeted tests for modified files to provide fast feedback, then run the full suite before concluding:
| Stack / Tool | Targeted Single-File Test Command | Full Project Test Suite Command |
|---|---|---|
| Node.js (Vitest) | npm test -- path/to/file.test.ts |
npm test |
| Node.js (Jest) | npx jest path/to/file.test.ts |
npm test |
| Python (Pytest) | pytest tests/test_file.py -k "test_name" |
pytest |
| Django | python manage.py test app.tests.TestClass |
python manage.py test |
| Go | go test -v ./pkg/service -run TestFunctionName |
go test ./... |
| Rust | cargo test test_name |
cargo test |
| .NET C# | dotnet test --filter "FullyQualifiedName~TestMethod" |
dotnet test |
| PHP (PHPUnit) | vendor/bin/phpunit tests/UserTest.php |
vendor/bin/phpunit |
2. The Testing Pyramid & Mocking Boundaries
/\
/ \ E2E Tests (Crucial user journeys only)
/────\
/ \ Integration Tests (API routes + DB queries + contracts)
/────────\
/ \ Unit Tests (Pure domain logic, utilities, edge cases)
/────────────\
Mocking Rules
- Mock External Boundaries Only: Mock third-party payment gateways, email delivery, and cloud storage.
- Do NOT Mock Pure Logic: Never mock internal business functions or data transformers; test them with real inputs and assert exact outputs.
- Use Deterministic Factories: Use factories with fixed seeds; avoid random numbers (
Math.random()) or unpinned system clocks in test assertions.
3. Non-Negotiable Testing Invariants
- Zero Fabrication: Never state "All tests passed" without executing the test command and confirming that the process exited with code 0.
- Regression Assertion for Bugfixes: Every bug fix must include an automated regression test reproducing the original bug condition and asserting its resolution.
- Clean Teardown: Ensure tests clean up temporary files, mock servers, and database records to prevent cross-test pollution.
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.
- 2d ago First seen · 55 lines · 23 tokens per session scan A 00b1111d01f1
testing is a skill published in the GitHub repository AmanKtyr/Tailor (3 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 598 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…