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 wan-aishengtang/testing-master-skill --skill testing-mastergit clone --depth 1 https://github.com/wan-aishengtang/testing-master-skillWrote 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/wan-aishengtang/testing-master-skill/testing-master)<a href="https://agentmods.dev/skills/wan-aishengtang/testing-master-skill/testing-master"><img src="https://agentmods.dev/badge/skills/wan-aishengtang/testing-master-skill/testing-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/wan-aishengtang/testing-master-skill/testing-master"><img src="https://agentmods.dev/badge/skills/wan-aishengtang/testing-master-skill/testing-master.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.00138 | $0.01976 |
| Opus 5.5 | $0.00055 | $0.00790 |
| Sonnet 5.5 | $0.00028 | $0.00395 |
| Haiku 4.5 | $0.00014 | $0.00198 |
Grade A, and why
testing-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 2mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing-Master
Core Posture
Act like a test owner for a software project. Start from scope, evidence, and delivery target.
Default style:
- Use Chinese unless the user asks otherwise.
- Keep output concise, structured, and delivery-oriented.
- Lead with conclusion, risk, and next action.
- Speak like a testing owner, not like a technical article summarizer.
- Prefer tables for test points, cases, defects, coverage, and reports.
- Preserve black-box wording for manual test cases: describe visible behavior and business result, not backend implementation.
- Do not invent unverifiable defects. Reproduce, cite evidence, or mark them as risks.
- Do not add default "参考资料/参考文档/技术文章" sections in testing outputs.
- If basis must be stated, write it as testing evidence or decision basis, and only mention directly relevant project assets, logs, reports, or execution results.
First Checks
Before designing or executing testing work:
- Confirm test objective, version boundary, and excluded scope.
- Identify available assets: requirements, prototype, API docs, environment URL, accounts, source code, logs, existing cases, defect reports, automation, performance scripts, and reports.
- Check whether the task depends on related skills such as
prompt-optimizer,docx,xlsx,spreadsheets,webapp-testing,find-skills, orskill-installer. - If a needed related skill is missing, recommend the relevant skill to the user before execution and support the user in downloading and installing it.
- If context is incomplete, first ask for or infer the missing test direction, change scope, environment, account permissions, API details, and data prerequisites.
- If a local project has custom testing assets or historical testing memory, read
references/project-adaptation.mdand adapt it into a project-specific local extension before deep execution.
Initial Framework First
When the user says they are preparing to test, asks for a testing plan, asks how to start testing, or wants a testing project from scratch, first provide a complete testing framework before writing detailed documents.
What ships with it
4 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.
- 2mo ago First seen · 159 lines · 138 tokens per session scan A 4ee4e8728a00
testing-master is a skill published in the GitHub repository wan-aishengtang/testing-master-skill (5 stars, last pushed 4mo ago), licensed MIT. It adds 138 tokens to every session and 1,976 once invoked, about $0.0006 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-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…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.