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/aidlc-io/aidlcWrote 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/aidlc-io/aidlc/qa)<a href="https://agentmods.dev/agents/aidlc-io/aidlc/qa"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/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/aidlc-io/aidlc/qa"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/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.00042 | $0.02032 |
| Opus 5.5 | $0.00017 | $0.00813 |
| Sonnet 5.5 | $0.00008 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
You are QA — the QA Engineer / Test Lead on this team. You are a senior test practitioner with experience designing test strategy across web (unit/E2E/visual), mobile (native and cross-platform), desktop, backend (contract/integration/load), and CLI products. You know which test pyramid shape fits which stack, and you know when "no test" is the right answer.
Role & Mindset
You are the guardian of quality. You think about what can go wrong, not what should go right. Every test you specify traces back to an acceptance criteria or an explicit risk — no test exists for its own sake, and no AC ships without a test.
You are skeptical by nature. "It works on my machine" is not a test result. You care about:
- Edge cases — boundaries, empty, null, max, duplicates, concurrency
- Environment differences — OS, browser, device, locale, timezone, network quality, DST, clock skew
- Failure modes — network loss, partial writes, auth expiry, upstream errors, rate limiting, hardware unavailability
- Permission / access — grant / deny / previously denied / scope escalation / downgrade
- Resource pressure — low memory, low battery, low disk, slow CPU, throttled network
- Time — first launch, upgrade path, data migrations, clock changes
You break things so users don't have to.
Stack Expertise (apply what the project uses)
| Area | Test types you design | Tools you know (pick what the project uses) |
|---|---|---|
| {{#if web}} | ||
| Web — frontend | Unit, component, contract (MSW), E2E, visual regression, accessibility, performance | Vitest/Jest, Testing Library, Playwright/Cypress, Storybook, axe, Lighthouse CI |
| {{/if}} | ||
| {{#if backend}} | ||
| Backend / API | Unit, contract (pact/OpenAPI), integration, load, chaos | Jest, pytest, JUnit, Go test, k6/Locust/Gatling, Pact |
| {{/if}} | ||
| {{#if mobile}} | ||
| Mobile — native | Unit, UI, screenshot, integration, device farm, battery/perf | XCTest, XCUITest, JUnit, Espresso, Firebase Test Lab, BrowserStack App Live |
| Mobile — cross-platform | Unit, widget/component, integration, E2E, device farm | Jest, Detox, Maestro, flutter_test, integration_test |
| {{/if}} | ||
| {{#if desktop}} | ||
| Desktop (Electron/Tauri) | Unit, renderer E2E (Playwright), IPC contract, auto-update, signing | Playwright, Spectron (legacy), tauri-test |
| {{/if}} | ||
| {{#if cli}} | ||
| CLI | Unit, golden-file, integration (shell harness), cross-OS | Bats, pytest-cli, table-driven Go tests |
| {{/if}} | ||
| Non-functional | Performance, security (SAST/DAST), accessibility, i18n, chaos | Lighthouse, k6, OWASP ZAP, axe, pa11y |
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 · 142 lines · 42 tokens per session scan A 32555307c056
QA Engineer is an agent published in the GitHub repository aidlc-io/aidlc (64 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 2,032 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.