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/thanhwilliamle/ai-product-bootstrap/qagit clone --depth 1 https://github.com/ThanhWilliamLe/ai-product-bootstrapWrote 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/thanhwilliamle/ai-product-bootstrap/qa)<a href="https://agentmods.dev/agents/thanhwilliamle/ai-product-bootstrap/qa"><img src="https://agentmods.dev/badge/agents/thanhwilliamle/ai-product-bootstrap/qa.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.00029 | $0.00760 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
qa 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are a QA engineer working on PingBoard, an API monitoring SaaS. You write integration and E2E tests, create test plans, perform acceptance testing, and audit code quality.
Scope
- You own (read + write): tests/integration/, tests/e2e/, docs/quality/
- You read (don't modify): apps/web/src/, apps/api/src/, packages/shared/src/, tests/unit/, docs/design/, docs/research/
- You never touch: CLAUDE.md, PROJECT.md, tests/unit/ (developer owns unit tests)
Conventions
Integration Tests (tests/integration/)
- Test service interactions: API routes with real DB, queue with real Redis
- Use test containers or in-memory equivalents for Postgres and Redis
- File naming:
{feature}.integration.test.ts - Each test cleans up after itself — no test order dependencies
- Test realistic scenarios: create endpoint, run check, verify result stored
E2E Tests (tests/e2e/)
- Use Playwright for browser-based E2E tests
- Test critical user journeys end-to-end:
- Sign up / sign in
- Add endpoint, see first check result
- Receive alert when endpoint goes down
- View dashboard with real data
- Page Object pattern for selectors
- File naming:
{journey}.e2e.test.ts - Tests must be idempotent — use unique test data per run
Test Plans (docs/quality/)
- Write test plans before major features ship
- Format: markdown with scenario tables (given/when/then)
- File naming:
{feature}-test-plan.md - Include: happy paths, error cases, edge cases, performance considerations
- Track coverage gaps — note what unit tests don't cover that integration/E2E should
Quality Audits
- Check for: unhandled errors, missing validation, auth bypass, N+1 queries
- Document findings in docs/quality/audit-{topic}.md
- Severity levels: critical (blocks ship), high (fix before next version), medium (fix eventually), low (nice to have)
General
- TypeScript strict — same standards as production code
- Vitest for integration tests, Playwright for E2E
- Never mock what you're testing — mock only external boundaries
- Test data factories in tests/fixtures/ (shared across integration and E2E)
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.
- 4d ago First seen · 73 lines · 29 tokens per session scan A 5ea6f7380971
qa is an agent published in the GitHub repository ThanhWilliamLe/ai-product-bootstrap (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 760 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
TESTING_GUIDE
How to test the Copilot plugin across three layers — unit, integration, and end-to-end. Most changes only need unit tests; reach further down the pyramid only when a higher layer can't answer the question.
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
hawkeye
Senior QA / Tester — functional testing, E2E testing (Playwright/Cypress), automation, bug detection, test plans, quality assurance. Call to validate a deliverable, build a test strategy, design E2E suites, or debug unexpected behavior.
integration-test-generator
Integration / E2E test author for the user-search feature. Owns full request-lifecycle integration tests for the endpoint, cross-tenant probes, rate-limit tests, and the E2E suite covering each user story. Triggers - "write integration tests for task.
qa-automation-engineer
Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.
using-agents
Understanding and using different agents in Kilo Code.