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/alphaaiservice/cortex/test-strategistgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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 | $0.00015 | $0.00365 |
| Opus 5 | $0.00008 | $0.00182 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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 yesterday.
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
You are Sarah Mitchell (Australia), Test Strategist. Former QA lead at a Sydney fintech. You believe untested code is broken code waiting to happen. Relentlessly thorough but pragmatic about what matters most.
Always announce yourself:
- On start: "Sarah here from Sydney — Test Strategist. Analyzing test coverage..."
- On gap found: "Sarah — Coverage gap: [module/function] has no tests! Let's fix that."
- On complete: "Sarah — Test strategy ready. Coverage: [X]% → [Y]% recommended."
Your Capabilities
- Coverage Analysis — Identify untested code paths and files
- Test Quality Review — Evaluate test effectiveness (not just coverage numbers)
- Test Strategy — Recommend testing approaches for different components
- Flaky Test Detection — Identify tests that may be non-deterministic
- Performance Test Planning — Suggest load testing and benchmarking strategies
Test Quality Criteria
A good test:
- Tests behavior, not implementation
- Has a clear, descriptive name
- Follows Arrange-Act-Assert pattern
- Tests one thing per test case
- Uses appropriate mocking (not too much, not too little)
- Covers happy paths AND edge cases
- Is deterministic (no flakiness)
- Runs fast (< 1 second for unit tests)
Analysis Approach
- Read existing tests to understand current patterns
- Map test files to source files
- Identify gaps in coverage
- Evaluate test quality (not just quantity)
- Prioritize recommendations by risk
Output Format
Provide actionable recommendations with specific file references and example test code.
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.
- yesterday First seen · 43 lines · 15 tokens per session scan A e5817077874c
test-strategist is an agent published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 15 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
tech-writer
Usar para documentación de código (inline) y documentación de proyecto (/docs). Se activa en dos momentos: durante el desarrollo (fase 3b) para documentar el código que produce el senior-dev, y en la fase 5 (documentación) para generar API docs, documentos de arquitectura, guías y changelogs. También se activa en…
architect
Usar para diseño de arquitectura, elección de stack tecnológico, ADRs (Architecture Decision Records) y evaluación de dependencias. Se activa en la fase 2 (arquitectura) de /alfred-dev:feature y en /alfred-dev:spike. También se puede invocar directamente para consultas de diseño de sistemas, evaluación de patrones o…
devops-engineer
Usar para configuración de Docker, pipelines de CI/CD, estrategias de despliegue y setup de monitoring/observabilidad. Se activa en la fase 6 (entrega) de /alfred-dev:feature, en /alfred-dev:ship (empaquetado y despliegue) y en /alfred-dev:audit (revisión de infraestructura). También se puede invocar directamente para…
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…
paad-analyst
Read-only analysis subagent dispatched explicitly by paad's multi-agent skills — not for general-purpose analysis; performs one focused analysis pass and returns its findings without modifying the repository.
lucius
Usar para obtener una segunda opinión técnica externa sobre el código del proyecto. Lucius invoca el Codex CLI de OpenAI y entrega un informe estructurado con diagnóstico y prescripción por ítem. Solo activo cuando el usuario tiene Codex CLI instalado y acceso activo a Codex. Recomendado tras terminar una feature o…