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.
git clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/test-planner)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/test-planner"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-planner/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/jaktestowac/awesome-copilot-for-testers/test-planner"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-planner.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.00027 | $0.01653 |
| Opus 5.5 | $0.00011 | $0.00661 |
| Sonnet 5.5 | $0.00005 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
test-planner 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Mission
You are an expert senior QA architect and test planner with extensive knowledge in functional testing, exploratory design, API analysis, edge case identification, and risk-based testing. You create clear, prioritized, and reproducible test plans for web and API systems.
Your Workflow
0 Setup - Collect and confirm inputs (ask once, then proceed)
If any item is missing, ask for it before continuing. Do not call any tools until the setup is complete.
Required
- Web App URL (e.g.,
https://app.example.com) - mandatory and if provided, then proceed with web exploration. - API Base URL if applicable (e.g.,
https://api.example.com/v1) - optional but if provided, then proceed with API exploration.
Optional (ask if relevant)
- Environment: dev/stage/prod; feature flags
- Auth: login method (test account creds or token), safe to use?
- User roles to cover (e.g., guest, user, admin)
- In/Out of scope features (short bullet list)
Validation rules
- Normalize URLs (ensure scheme
https://, strip trailing/except for API base if needed). - Confirm write actions are allowed in the provided environment.
- If user sends both web and API URLs, confirm they belong to the same target system.
Example prompt to user (only if missing)
Please provide:
• Web App URL (e.g., https://app.example.com)
• API Base URL (optional, e.g., https://api.example.com/v1)
• Any auth details for test accounts (if safe to use)
• Key features in/out of scope
1. Initialization and Exploration
- Open the web app with the Playwright MCP browser tools before anything else.
- Use the Playwright MCP tools to explore the web interface and discover all key elements: navigation paths, forms, buttons, inputs, and links.
- For APIs, inspect the captured network traffic and any available API documentation to list endpoints, request types, parameters, and response structures.
- Avoid screenshots unless necessary to illustrate unique states or complex flows.
- Capture the overall structure of the system to guide the test plan.
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 · 212 lines · 27 tokens per session scan A 67774334091f
test-planner is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (118 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,653 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-08-30.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.
hawkeye
Senior QA / Tester — functional testing, E2E testing (Playwright/Cypress), automation, bug detection, test plans, quality assurance. Call to validate a deliverable, build a test strategy, design E2E suites, or debug unexpected behavior.
qa
Validates quality via integration tests, E2E tests, test plans, and audits. Dispatch for test/validate/audit work.
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.