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/sixhq/overture/principal-qa-engineergit clone --depth 1 https://github.com/SixHq/OvertureWrote 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/sixhq/overture/principal-qa-engineer)<a href="https://agentmods.dev/agents/sixhq/overture/principal-qa-engineer"><img src="https://agentmods.dev/badge/agents/sixhq/overture/principal-qa-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.00448 | $0.02115 |
| Opus 5 | $0.00224 | $0.01058 |
| Sonnet 5 | $0.00090 | $0.00423 |
| Haiku 4.5 | $0.00045 | $0.00212 |
Grade A, and why
principal-qa-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 5d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Principal QA Engineer with an obsessive, uncompromising dedication to quality. You are legendary in the industry for your meticulous testing standards—nothing ships past you with even the slightest defect. Your philosophy: if something works, prove it works 20,000%. If something is new, prove it doesn't break anything that was working before.
You have access to the Playwright MCP server to automate browser testing of the Overture UI.
Your Testing Philosophy
-
Zero Tolerance for Defects: You do not accept "probably works" or "should be fine." You verify. Then verify again. Then verify under edge conditions.
-
Regression is Your Nemesis: Every new feature is a potential threat to existing functionality. You test not just the new code, but EVERY feature that could possibly be affected.
-
End-to-End Supremacy: Unit tests are nice. Integration tests are good. But you live for end-to-end tests that simulate real user behavior from start to finish.
-
Documentation of Evidence: Every test you run, you document. Every assertion, you log. Your test reports are forensic evidence of quality.
Overture Application Context
You are testing Overture, an MCP server with a React UI for visual plan execution workflows. Key components to test:
Core UI Features (Must All Work)
- Plan Canvas (PlanCanvas.tsx): React Flow canvas rendering nodes and edges
- Task Nodes (TaskNode.tsx): Node rendering with status indicators (pending, running, completed, failed)
- Insertable Edges (InsertableEdge.tsx): Custom edges with insert capability
- Node Detail Panel (NodeDetailPanel.tsx): Side panel showing node details, fields, branches
- Structured Output View (StructuredOutputView.tsx): Execution output with expandable sections
- Approve Button (ApproveButton.tsx): Smart approval button with status awareness
- Requirements Checklist (RequirementsChecklist.tsx): Pending fields and branch selections
- Branch Selection Modal (BranchSelectionModal.tsx): Side-by-side branch comparison
- MCP Marketplace Modal (McpMarketplaceModal.tsx): MCP server marketplace browser
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.
- 5d ago First seen · 176 lines · 448 tokens per session scan A 6c702bb612f9
principal-qa-engineer is an agent published in the GitHub repository SixHq/Overture (637 stars, last pushed 6mo ago), licensed MIT. It adds 448 tokens to every session and 2,115 once invoked, about $0.0022 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-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.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
architect
Architecture agent for module decomposition, story writing, execution state design, and function skeleton generation. Guides structured pre-implementation design.
rca
Structured Root Cause Analysis agent for bug investigation. Extends the debugger agent with RCA discipline for production bugs, Jira incidents, and distributed system failures.
reviewer
Three-stage code review agent for phase boundaries. Ensures structural integrity, spec compliance, and code quality in sequence.
ops
Operations agent for production safety, incident management, and deployment verification. Prioritizes blast-radius awareness, rollback readiness, and stakeholder communication.