A set of rules for testing software, including finding the project’s test tool, running focused tests for changed code, and running the complete test suite. A test suite is the collection of automated checks for a project.

Use it when adding features, fixing bugs, refactoring, or checking code in projects built with tools such as Vitest, Jest, Pytest, Go, Rust, .NET, Django, or PHPUnit.

It provides quick feedback while editing and verifies the whole project before work is considered complete, instead of relying on untested changes.

How AmanKtyr/Tailor configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to AmanKtyr/Tailor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AmanKtyr/Tailor/main/.agents/skills/testing/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/AmanKtyr/Tailor

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/amanktyr/tailor/testing/github.svg)](https://agentmods.dev/skills/amanktyr/tailor/testing)

Your own site

<a href="https://agentmods.dev/skills/amanktyr/tailor/testing"><img src="https://agentmods.dev/badge/skills/amanktyr/tailor/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/amanktyr/tailor/testing"><img src="https://agentmods.dev/badge/skills/amanktyr/tailor/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.01380
Opus 5.5	$0.00016	$0.00552
Sonnet 5.5	$0.00008	$0.00276
Haiku 4.5	$0.00004	$0.00138

Measured 10d ago against content hash 3b645a856f05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 10d 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.

.agents/skills/testing/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 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. Flaky tests are liabilities. 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.

Read the full file on GitHub · 123 lines

Changes

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.

10d ago Changed · +42 lines · +8 tokens per session 3b645a856f05
1mo ago Changed · +26 lines · +9 tokens per session 27734c926a27
1mo ago First seen · 55 lines · 23 tokens per session scan A 00b1111d01f1

Subscribe to this mod's changes

testing is a skill published in the GitHub repository AmanKtyr/Tailor (6 stars, last pushed 11d ago), licensed MIT. It adds 40 tokens to every session and 1,380 once invoked, about $0.0002 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

Tailor: Skill for Claude Code