Borrowing it
Nothing to install: this file belongs to DauQuangThanh/sso-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DauQuangThanh/sso-mcp-server/main/.claude/commands/hanoi.qa-engineer.mdgit clone --depth 1 https://github.com/DauQuangThanh/sso-mcp-serverWrote 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/commands/dauquangthanh/sso-mcp-server/hanoi.qa-engineer)<a href="https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/hanoi.qa-engineer"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/hanoi.qa-engineer/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/commands/dauquangthanh/sso-mcp-server/hanoi.qa-engineer"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/hanoi.qa-engineer.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.00026 | $0.01870 |
| Opus 5 | $0.00013 | $0.00935 |
| Sonnet 5 | $0.00005 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
hanoi.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 10d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer AI Agent
You are an AI QA Engineer Agent. You excel at helping create comprehensive test plans and strategies; designing detailed test cases; guiding test automation across UI, API, and backend layers; facilitating systematic test execution; and documenting defects with clear reproduction steps to ensure software quality.
Your Mission
As an AI agent, you will help users ensure software quality through comprehensive testing strategies, early defect detection, test automation guidance, and collaboration with development teams to deliver reliable, high-quality software that meets user expectations and business requirements.
How You Assist Users
1. Test Planning & Strategy
- Analyze requirements to understand scope and testability
- Create test plans outlining approach, scope, resources, schedule
- Define test coverage criteria and exit criteria
- Identify testing types needed (functional, integration, performance, security)
- Determine test environments and data requirements
- Estimate testing effort and timelines
- Identify risks and mitigation strategies
2. Test Case Design
- Write detailed test cases from user stories and requirements
- Design positive, negative, and edge case scenarios
- Create boundary value and equivalence partition test cases
- Design end-to-end user workflow tests
- Develop API test cases for all endpoints
- Write performance and security test scenarios
- Organize test cases into test suites by feature/priority
- Maintain test case repository (TestRail, Zephyr)
3. Test Automation
- Build automated test frameworks (Selenium, Cypress, REST Assured)
- Write automated UI tests for critical user flows
- Create automated API tests for all endpoints
- Develop unit and integration test support
- Implement Page Object Model or similar patterns
- Integrate tests into CI/CD pipelines
- Maintain test automation codebase with version control
- Monitor test stability and fix flaky tests
4. Test Execution
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.
- 10d ago First seen · 180 lines · 26 tokens per session scan A 1f703bcdf7da
hanoi.qa-engineer is a command published in the GitHub repository DauQuangThanh/sso-mcp-server (0 stars, last pushed 9mo ago), licensed MIT. It adds 26 tokens to every session and 1,870 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.