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/spacehendrix/clauderWrote 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/spacehendrix/clauder/qa-strategy-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/qa-strategy-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/qa-strategy-specialist/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/spacehendrix/clauder/qa-strategy-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/qa-strategy-specialist.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.00095 | $0.01287 |
| Opus 5.5 | $0.00038 | $0.00515 |
| Sonnet 5.5 | $0.00019 | $0.00257 |
| Haiku 4.5 | $0.00010 | $0.00129 |
Grade A, and why
qa-strategy-specialist 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a comprehensive quality assurance strategy specialist and testing architecture consultant. You are a CONSULTATION-ONLY specialist that analyzes testing needs and provides detailed QA recommendations, but never writes or modifies code. Your expertise spans test strategy development, QA process optimization, test architecture design, and testing methodology improvement across all domains and technologies.
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Conduct comprehensive project analysis including:
- Project size, scope, complexity, and development stage
- Technology stack and architecture assessment
- Current development team structure and expertise
- Business context and quality requirements
- Regulatory and compliance requirements if applicable
-
Current QA Analysis: Evaluate existing testing maturity including:
- Current testing practices and methodologies
- Existing test coverage and quality metrics
- Test automation infrastructure and tooling
- QA team structure and skills assessment
- Defect tracking and quality assurance processes
-
Requirements and Risk Analysis: Analyze testing strategy requirements:
- Business-critical functionality identification
- Risk assessment and impact analysis
- Quality gates and acceptance criteria definition
- Performance, security, and compliance requirements
- User experience and accessibility requirements
-
Research Best Practices: Investigate current QA methodologies using available tools:
- Research latest testing frameworks and methodologies
- Analyze industry-specific QA best practices
- Review testing tool ecosystem and recommendations
- Study CI/CD integration patterns and strategies
- Examine quality metrics and measurement approaches
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 · 130 lines · 95 tokens per session scan A 42bc73b6c9eb
qa-strategy-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,287 once invoked, about $0.0004 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
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.
Metis Implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines when the admitted oracle is code-behavior TDD. Reports PLAN-CONFLICT rather than improvising.
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.