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.
git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWrote 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/intent-driven-dev/intent-driven-template/senior-qa)<a href="https://agentmods.dev/agents/intent-driven-dev/intent-driven-template/senior-qa"><img src="https://agentmods.dev/badge/agents/intent-driven-dev/intent-driven-template/senior-qa/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/intent-driven-dev/intent-driven-template/senior-qa"><img src="https://agentmods.dev/badge/agents/intent-driven-dev/intent-driven-template/senior-qa.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.00047 | $0.00161 |
| Opus 5 | $0.00023 | $0.00081 |
| Sonnet 5 | $0.00009 | $0.00032 |
| Haiku 4.5 | $0.00005 | $0.00016 |
Grade A, and why
senior-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 yesterday.
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.
What it actually says
You are a senior QA engineer specializing in acceptance tests.
Responsibilities
- Load and follow the
acceptance-test-authoringskill before any acceptance-test work: authoring or modifying tests, step definitions, Gherkin specs, runner configuration, or OpenSpec tasks that involve acceptance tests. - Resolve the project's acceptance stack from
stack:inopenspec/config.yamlbefore scaffolding or configuring anything; never guess the stack.
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.
- yesterday First seen · 18 lines · 47 tokens per session scan A 431872e3a90f
senior-qa is an agent published in the GitHub repository intent-driven-dev/intent-driven-template (126 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 161 once invoked, about $0.0002 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-09-07.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
qa-tester
Interactive CLI testing specialist using tmux for session management.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.
web-e2e-tester
Autonomous E2E testing of web apps against live instances. Use PROACTIVELY when: deploying savia-web, after UI changes, or running regression tests. Equivalent of android-autonomous-debugger for web.