Borrowing it
Nothing to install: this file belongs to pavel-molyanov/molyanov-ai-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pavel-molyanov/molyanov-ai-dev/main/.agents/skills/test-master/SKILL.mdgit clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-devWrote 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/pavel-molyanov/molyanov-ai-dev/test-master)<a href="https://agentmods.dev/skills/pavel-molyanov/molyanov-ai-dev/test-master"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/test-master/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/pavel-molyanov/molyanov-ai-dev/test-master"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/test-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00876 |
| Opus 5.5 | $0.00027 | $0.00350 |
| Sonnet 5.5 | $0.00014 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
test-master 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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Master
Decide What to Protect
Tests protect observable behavior or another explicit contract that must survive change. Trace each selected scenario to the user request, user-spec, or changed project contract.
Automated tests apply only to deterministic executable code; LLM-produced results and presentation-only layout use agent, manual, or visual verification instead.
Freely editable copy, presentation-only markup or styles, constants that merely repeat their source value, and framework behavior normally have no test subject. They become testable when an explicit user, accessibility, legal, safety, protocol, or project requirement makes their presence or semantics invariant. Test that contract at an observable boundary rather than freezing implementation shape or exact wording.
Choose the Smallest Reliable Boundary
Protect each distinct risk once at the smallest boundary that can reproduce it:
| Boundary | Use when the risk depends on |
|---|---|
| Unit | One unit's calculation, decision, validation, transformation, or error behavior |
| Integration | An API, database, filesystem, queue, service contract, or collaborating components |
| E2E | A critical user journey or behavior that needs the real application stack |
| Smoke | Successful startup, initialization, deployment, or minimal system integration |
Do not repeat the same risk at several levels for pyramid completeness. A characterization test may pass before a refactor when its purpose is to prove existing behavior remains unchanged.
When authoring a selected type, apply its conditional guide:
- unit-tests.md — unit structure, dependency boundaries, and mocking;
- integration-tests.md — real component boundaries, fixtures, external services, and cleanup;
- e2e-tests.md — journeys, environment, selectors, and execution;
- smoke-tests.md — minimal startup and infrastructure coverage.
What ships with it
5 files 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.
- 6d ago Changed · +16 lines · +5 tokens per session 93467d0c634b
- 1mo ago First seen · 68 lines · 63 tokens per session scan A 5e64a4015f98
test-master is a skill published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 876 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
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…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.