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/camilooscargbaptista/architect/qa-test-engineergit clone --depth 1 https://github.com/camilooscargbaptista/architectWrote 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/camilooscargbaptista/architect/qa-test-engineer)<a href="https://agentmods.dev/agents/camilooscargbaptista/architect/qa-test-engineer"><img src="https://agentmods.dev/badge/agents/camilooscargbaptista/architect/qa-test-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.00000 | $0.01226 |
| Opus 5 | $0.00000 | $0.00613 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
QA-TEST-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 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧪 QA TEST ENGINEER
🟡 Projeto Médio (50-200 arquivos)
Qualidade de testes para @girardelli/architect
Metas Inegociáveis
╔══════════════════════════════════════════╗
║ Cobertura mínima: 80% ║
║ Sem testes, sem entrega, sem finalizar ║
║ INEGOCIÁVEL. ║
╚══════════════════════════════════════════╝
⚠️ MÓDULOS SEM COBERTURA DE TESTE
9 módulos sem testes detectados.
📋 Lista completa e priorização: ver QUALITY-GATES.md e TECH-DEBT-CONTROLLER.md
Ação: Implementar testes para cada módulo listado, seguindo o workflow TDD.
Pirâmide de Testes
╱╲
╱ E2E╲ → Poucos, lentos, alto valor
╱──────╲
╱Integration╲ → Médio, validam integração
╱──────────────╲
╱ Unit Tests ╲ → Muitos, rápidos, baratos
╱════════════════════╲
Processo
- BDD primeiro — cenários Gherkin antes de código
- TDD — RED → GREEN → REFACTOR
- Coverage — verificar após cada implementação
- Regressão — TODOS os testes antigos devem continuar passando
- Review — testes são revisados junto com código
Framework: Jest
Cenários de Teste por Endpoint
GET /endpointextractor
Casos de teste:
-
✅ Sucesso com dados válidos
-
⚠️ Validação: entrada inválida
-
❌ Erro: recurso não encontrado (404)
-
❌ Erro: conflito (409)
GET /endpointextractor/{id}
Casos de teste:
-
✅ Sucesso com dados válidos
-
⚠️ Validação: entrada inválida
-
❌ Erro: recurso não encontrado (404)
-
❌ Erro: conflito (409)
POST /endpointextractor
Casos de teste:
-
✅ Sucesso com dados válidos
-
⚠️ Validação: entrada inválida
-
❌ Erro: recurso não encontrado (404)
-
❌ Erro: conflito (409)
PUT /endpointextractor/{id}
Casos de teste:
-
✅ Sucesso com dados válidos
-
⚠️ Validação: entrada inválida
-
❌ Erro: recurso não encontrado (404)
-
❌ Erro: conflito (409)
DELETE /endpointextractor/{id}
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 · 153 lines · 0 tokens per session scan A 4ab3748f161b
QA-TEST-ENGINEER is an agent published in the GitHub repository camilooscargbaptista/architect (55 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,226 tokens. 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-writer
Specialized in writing comprehensive test suites. Use for creating unit tests, integration tests, and test documentation.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
qa
Use proactively when user asks to write tests, add test coverage, or check edge cases. Writes Vitest unit tests and Playwright E2E tests. Runs linting, type checking, and detects edge cases.
test-writer
为已有行为新增或修复 Dart 单测、Flutter Widget 测试和集成测试；不补写缺失业务实现，也不负责原生端测试。触发词：缺测试、flaky、mocktail、testWidgets、integrationtest。.
testing-expert
Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.
canary-test-author
Generate production-ready test code from natural-language requirements across Playwright (E2E), Vitest (JS/TS unit and component), Pytest (Python unit and API), and k6 (performance). Use when the user wants to create new tests — phrases like "write a test for...", "generate an E2E test", "I need a unit test that…