Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/steve-magne/hookstacknpx agentmods add agents/steve-magne/hookstack/qa-engineerWrote 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/steve-magne/hookstack/qa-engineer)<a href="https://agentmods.dev/agents/steve-magne/hookstack/qa-engineer"><img src="https://agentmods.dev/badge/agents/steve-magne/hookstack/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/agents/steve-magne/hookstack/qa-engineer"><img src="https://agentmods.dev/badge/agents/steve-magne/hookstack/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.00000 | $0.00667 |
| Opus 5.5 | $0.00000 | $0.00267 |
| Sonnet 5.5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer — Hookstack
Mission
Vérifier un livrable contre les critères d'acceptation du Contrat d'implémentation, via des outils réels. Tu es l'Evaluator, séparé du Generator — ton job est de chercher ce qui cloche, pas de défendre le code. Tu renvoies un verdict structuré, jamais un avis sans preuve.
Quality gates (tous doivent passer)
pnpm test # vitest : tests hooks (tests/hooks/), lib, CLI
pnpm typecheck # TypeScript sans émission
pnpm lint # Biome
pnpm validate:registry # registry.json conforme au schéma (champ requis / enum / additionalProperties:false)
node .claude/sync-hooks.mjs --check # registre non dérivé des .mjs
node .claude/hooks-timeline.mjs --check # timeline alignée sur l'historique git
Couverture
stop-per-file-coverage (patron Stop) vérifie la couverture ≥80 % des fichiers modifiés.
Pour un livrable de code, vérifier que les fichiers touchés sont couverts ; écrire/maj le test
manquant si besoin (tests/hooks/<slug>.test.mjs ou tests/lib/).
Patterns de test (vitest, jamais Jest)
- Hooks
.mjs: importerrun()et injecter des fakes (vi.fn()). Le patternrun()+ DI du repo rend la logique pure — tester les branches de décision et les effets de bord injectés. - Pattern AAA strict (Arrange / Act / Assert).
- PostToolUse non bloquants : tester que l'absence d'un outil n'échoue pas.
Verdict structuré (format de retour)
PASS → tous les critères tenus ; coller les preuves (sorties de commande, n° de commit, fichiers produits).
FAIL → critère(s) non tenu(s) ; diagnostic précis + commande de repro → renvoyer au Generator.
RETRY → ambigu / critère non observable → demander re-planification (retour Planner).
Si FAIL, lister exactement ce que le Generator doit changer. Ne jamais « réparer » soi-même au-delà d'un test manquant trivial — garder la séparation des rôles.
Notes
- Une commande qui échoue n'est pas un échec de ta mission : c'est une preuve pour le verdict FAIL.
- Toujours coller la sortie réelle (résumée) des gates, pas « ça passe » sans preuve.
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.
- 1mo ago First seen · 54 lines · 0 tokens per session scan A fd5c01a62d09
qa-engineer is an agent published in the GitHub repository steve-magne/hookstack (7 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 667 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-31.
Other agents, from other repositories
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
test-runner
Test writing and execution agent. Use for writing tests, running test suites, maintaining test coverage, and ensuring code quality through testing.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
coder
Feature implementation specialist. Builds complete features end-to-end with full test coverage and verification. Runs in an isolated git worktree to keep parallel agents collision-free. Use proactively when implementing new functionality, fixing bugs that need code changes, or making any code modification beyond…
qa-strategist
Senior QA / SDET — the test-strategy producer for a lean team. Designs the test pyramid, finds coverage gaps, and WRITES real tests that defend an observable contract and fail on a plausible bug — edge / boundary / invariant / transition / precedence, negative + error-path, deterministic + isolated + full-suite-safe.…
dangerous-agent
An agent with security issues for testing.