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 georgekhananaev/claude-skills-vault --skill testing-automation-expertgit clone --depth 1 https://github.com/georgekhananaev/claude-skills-vaultWrote 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/georgekhananaev/claude-skills-vault/testing-automation-expert)<a href="https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/testing-automation-expert"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/testing-automation-expert/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/georgekhananaev/claude-skills-vault/testing-automation-expert"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/testing-automation-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 190 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 218 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 219 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 220 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 221 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 227 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 228 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 229 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 230 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00056 | $0.02076 |
| Opus 5.5 | $0.00022 | $0.00830 |
| Sonnet 5.5 | $0.00011 | $0.00415 |
| Haiku 4.5 | $0.00006 | $0.00208 |
Grade A, and why
testing-automation-expert 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- testing-automation-expert — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Automation Expert
Master production-grade testing strategies for Python and TypeScript applications. QA Architect level - design test ecosystems that scale.
When to Use
- Designing test strategies for features/projects
- Setting up pytest, Jest, Vitest, or Playwright
- Improving test coverage and quality
- Contract testing, accessibility, mutation testing
- CI/CD test pipeline optimization
- Test architecture review or refactoring
Triggers
/test-plan- Design test strategy for a feature/project/fixture-refactor- Optimize test fixture architecture/e2e-setup- Set up Playwright E2E testing/test-audit- Review test coverage and quality/contract-test- Set up Pact contract testing
Reference Files
Load the appropriate reference based on need:
| Category | Framework | Reference |
|---|---|---|
| Python | pytest | references/python-pytest.md |
| TypeScript | Jest | references/typescript-jest.md |
| TypeScript | Vitest | references/typescript-vitest.md |
| E2E | Playwright | references/e2e-playwright.md |
| Advanced | Contract/A11y/Mutation | references/specialized-testing.md |
Test Quality Checklists
Pre-Implementation Checklist
- Test strategy defined - unit, integration, E2E, contract boundaries clear
- Fixtures planned - factory functions, DB setup, cleanup
- Mocking strategy - mock at boundaries only, not internals
- Coverage targets - minimum 80% branches/lines/functions
- CI integration - tests run on every PR with sharding if >10min
- Flakiness detection - pytest-randomly / random test order enabled
Unit Test Checklist
- Tests isolated - no shared state between tests
- One assertion focus - test one behavior per test
- Descriptive names -
should_return_error_when_user_not_found - AAA pattern - Arrange, Act, Assert clearly separated
- Edge cases covered - null, empty, boundary values
- No external dependencies - DB, network, filesystem mocked
- Property-based tests - Hypothesis/fast-check for edge case discovery
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.
- 1mo ago First seen · 270 lines · 56 tokens per session scan A b8ebfd5ac20c
testing-automation-expert is a skill published in the GitHub repository georgekhananaev/claude-skills-vault (30 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 2,076 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-09-03.
Other skills, from other repositories
test-selection
Use this skill when someone describes a specific code path, feature, or bug and asks what kind of test to write for it — or when an audit or strategy engagement surfaces a testing gap and needs a recommendation for where to start. Trigger on "what test should I write for this", "unit or integration test for X", "our…
mirrord-ci
Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.
deploy-and-runtime-verification
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
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…
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.