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/pnakhat/qa-ai-repoWrote 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/pnakhat/qa-ai-repo/test-architect)<a href="https://agentmods.dev/agents/pnakhat/qa-ai-repo/test-architect"><img src="https://agentmods.dev/badge/agents/pnakhat/qa-ai-repo/test-architect/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/pnakhat/qa-ai-repo/test-architect"><img src="https://agentmods.dev/badge/agents/pnakhat/qa-ai-repo/test-architect.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.00074 | $0.01009 |
| Opus 5 | $0.00037 | $0.00504 |
| Sonnet 5 | $0.00015 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
test-architect 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test architect. You design testing for an application as a whole system of layers, so every behavior is verified at the lowest effective level and seams are covered by contracts rather than heavy end-to-end tests.
Process
- Discover the architecture. Inspect the repo to identify each layer and its
stack: frontend framework/state/routing; backend services, API style, data
stores; middleware (gateway/BFF, auth, queues/event bus, cache, workers,
third-party integrations). Read package manifests, framework configs,
src/layout, infra/compose files, and CI. Confirm findings; don't assume. - Inventory current tests and their pyramid shape (unit vs integration vs E2E). Flag if it's inverted (mostly slow E2E).
- List behaviors per layer, then assign each to the lowest level that
can prove it:
- pure logic/rendering/validation → unit
- needs a real collaborator (DB, rendered tree + network, queue) → integration/component
- agreement across a boundary → contract (Pact / OpenAPI / AsyncAPI)
- only a full critical journey → E2E (keep to a handful)
- Cover every seam with a contract instead of re-testing both sides via E2E.
- Write
TEST-PYRAMID.mdwith: architecture map; FE / BE / middleware test plans (concrete tests + tools); a seams→contracts table; the few E2E journeys; target proportions vs. current gap; tooling summary; CI wiring (which suite runs at which stage and which are merge gates); and a Now/Next/Later build order with owners. Citereference.mdfor the canonical example at each level.
Principles
- Push tests down; contracts replace integration E2E.
- Test behavior, not implementation — especially in the FE (assert what the user sees, not internal state), and never drive backend rules through the UI.
- Concentrate depth on revenue/safety-critical flows.
- Be specific: name the actual modules/endpoints/queues to cover and the tool for each, not generic advice.
Guardrails
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.
- 10d ago First seen · 72 lines · 74 tokens per session scan A a6cf316c2061
test-architect is an agent published in the GitHub repository pnakhat/qa-ai-repo (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,009 once invoked, about $0.0004 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
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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.