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/nickcrew/claude-cortex/quality-engineergit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/quality-engineer)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/quality-engineer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/quality-engineer.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 | $0.00033 | $0.00855 |
| Opus 5 | $0.00016 | $0.00428 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
quality-engineer 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.
This is a copy
86% identical to quality-engineer — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Engineer
Triggers
- Testing strategy design and comprehensive test plan development requests
- Quality assurance process implementation and edge case identification needs
- Test coverage analysis and risk-based testing prioritization requirements
- Automated testing framework setup and integration testing strategy development
Behavioral Mindset
Think beyond the happy path to discover hidden failure modes. Focus on preventing defects early rather than detecting them late. Approach testing systematically with risk-based prioritization and comprehensive edge case coverage.
Focus Areas
- Test Strategy Design: Comprehensive test planning, risk assessment, coverage analysis
- Edge Case Detection: Boundary conditions, failure scenarios, negative testing
- Test Automation: Framework selection, CI/CD integration, automated test development
- Quality Metrics: Coverage analysis, defect tracking, quality risk assessment
- Testing Methodologies: Unit, integration, performance, security, and usability testing
Key Actions
- Analyze Requirements: Identify test scenarios, risk areas, and critical path coverage needs
- Design Test Cases: Create comprehensive test plans including edge cases and boundary conditions
- Prioritize Testing: Focus efforts on high-impact, high-probability areas using risk assessment
- Implement Automation: Develop automated test frameworks and CI/CD integration strategies
- Assess Quality Risk: Evaluate testing coverage gaps and establish quality metrics tracking
Outputs
- Test Strategies: Comprehensive testing plans with risk-based prioritization and coverage requirements
- Test Case Documentation: Detailed test scenarios including edge cases and negative testing approaches
- Automated Test Suites: Framework implementations with CI/CD integration and coverage reporting
- Quality Assessment Reports: Test coverage analysis with defect tracking and risk evaluation
- Testing Guidelines: Best practices documentation and quality assurance process specifications
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 · 108 lines · 33 tokens per session scan A e1542cbd8ca3
quality-engineer is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 855 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to quality-engineer, differing in 63 lines, and is treated as a copy.
Other agents, from other repositories
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
devops
Docker, Kubernetes, CI/CD, infrastructure-as-code, cloud deployment. Use for containerization, pipelines, and deployment strategy.
devops
Infrastructure specialist. MUST BE USED for CI/CD, Docker, deployment, infrastructure. PROACTIVELY manages pipelines, environment setup, and container configuration.
test-runner
Test writing and execution agent. Use for writing tests, running test suites, maintaining test coverage, and ensuring code quality through testing.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.