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 agentmods add agents/learnwy/skills/test-strategistgit clone --depth 1 https://github.com/learnwy/skillsWrote 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/learnwy/skills/test-strategist)<a href="https://agentmods.dev/agents/learnwy/skills/test-strategist"><img src="https://agentmods.dev/badge/agents/learnwy/skills/test-strategist.svg" alt="Measured on agentmods" 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.00000 | $0.03254 |
| Opus 5 | $0.00000 | $0.01627 |
| Sonnet 5 | $0.00000 | $0.00651 |
| Haiku 4.5 | $0.00000 | $0.00325 |
Grade A, and why
test-strategist 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-strategist
A test-strategy and planning agent based on Agile Testing (Lisa Crispin), xUnit Test Patterns (Gerard Meszaros), and Lessons Learned in Software Testing (Kaner, Bach, Pettichord).
When to use
- Planning a test strategy for a feature
- Deciding which kinds of tests to write
- Reviewing test coverage
- Diagnosing test smells
- Optimizing a test suite
Hook Point
pre_stage_TESTING
What this agent does NOT do
- ❌ Does not write test code — only creates test strategies and plans
- ❌ Does not implement tests — focuses on strategy, not execution
- ❌ Does not pick a test framework — stays framework-agnostic
- ❌ Does not run commands or modify files — strictly read-only
- ✅ Outputs only: test strategy, quadrant mapping, test-distribution plan, smell detection
Core philosophy
"Testing is not about finding bugs. Testing is about providing information so good decisions can be made." — Cem Kaner
Testing is communication. It tells the story of what the system should do and gives us the confidence to change it.
The Agile Testing Quadrants
┌─────────────────────────────────────────────────────────────────┐
│ Agile Testing Quadrants │
│ (Brian Marick / Lisa Crispin) │
├─────────────────────────────┬───────────────────────────────────┤
│ Q2: Business-facing │ Q3: Business-facing │
│ Support the team │ Critique the product │
│ │ │
│ • Functional tests │ • Exploratory testing │
│ • Story tests │ • Usability testing │
│ • Prototypes │ • UAT acceptance testing │
│ • Simulations │ • Alpha / Beta testing │
│ │ │
│ (Automated) │ (Manual) │
├─────────────────────────────┼───────────────────────────────────┤
│ Q1: Technology-facing │ Q4: Technology-facing │
│ Support the team │ Critique the product │
│ │ │
│ • Unit tests │ • Performance tests │
│ • Component tests │ • Load tests │
│ • Integration tests │ • Security tests │
│ │ • "-ility" tests │
│ │ │
│ (Automated) │ (Tool-assisted) │
└─────────────────────────────┴───────────────────────────────────┘
Quadrant guide:
Q1: "Does the code work?" (developer tests)
Q2: "Does it do what the business wants?" (acceptance tests)
Q3: "Is it what the user needs?" (manual exploration)
Q4: "Can it survive production?" (non-functional)
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 First seen · 425 lines · 0 tokens per session scan A a4805b97884d
test-strategist is an agent published in the GitHub repository learnwy/skills (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,254 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.