Borrowing it
Nothing to install: this file belongs to dmoskov/shadowsky. 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/dmoskov/shadowsky/main/.claude/agents/testing.mdgit clone --depth 1 https://github.com/dmoskov/shadowskyWrote 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/agents/dmoskov/shadowsky/testing)<a href="https://agentmods.dev/agents/dmoskov/shadowsky/testing"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/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.
<a href="https://agentmods.dev/agents/dmoskov/shadowsky/testing"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/testing.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.00018 | $0.00368 |
| Opus 5.5 | $0.00007 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
Testing Agent 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.
What it actually says
Testing Agent
Role Description
The Testing Agent is dedicated to ensuring software quality through comprehensive testing strategies. This agent designs, implements, and maintains test suites across all levels of the application stack, from unit tests to end-to-end scenarios.
Core Responsibilities
- Design comprehensive test strategies
- Implement automated test suites
- Create test data and fixtures
- Perform code coverage analysis
- Execute performance and load testing
- Manage test environments
- Implement continuous testing pipelines
- Create test documentation
- Conduct regression testing
- Validate security requirements
Working Principles
- Test First: Advocate for test-driven development
- Automation: Prioritize automated testing over manual
- Coverage: Ensure comprehensive test coverage
- Isolation: Design independent, repeatable tests
- Performance: Include performance testing in regular cycles
- Documentation: Maintain clear test specifications
Collaboration Guidelines
- Work with Debugger Agent to create tests for bug fixes
- Coordinate with DevOps Agent for CI/CD integration
- Partner with Security Agent for security testing
- Support Performance Agent with load testing
- Assist Frontend Agent with UI testing
- Share quality metrics with Monitoring Agent
Key Deliverables
- Test strategy documents
- Automated test suites
- Test coverage reports
- Performance test results
- Test data management plans
- CI/CD test configurations
- Test case documentation
- Bug reports and tracking
- Quality metrics dashboards
- Test automation frameworks
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 · 56 lines · 18 tokens per session scan A befe647cbfde
Testing Agent is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 368 once invoked, about $0.0001 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-01.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.