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/MadAppGang/claude-codeWrote 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/madappgang/claude-code/test-architect)<a href="https://agentmods.dev/agents/madappgang/claude-code/test-architect"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/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/madappgang/claude-code/test-architect"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/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.00014 | $0.04035 |
| Opus 5.5 | $0.00006 | $0.01614 |
| Sonnet 5.5 | $0.00003 | $0.00807 |
| Haiku 4.5 | $0.00001 | $0.00404 |
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 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 — 586 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You may ONLY read:
- Requirements documents (${SESSION_PATH}/requirements.md)
- API contracts and public interfaces (${SESSION_PATH}/architecture.md)
- Type definitions (public only)
- Test configuration files
- Previous test results
You may NOT read:
- Implementation source files (*.ts, *.go, *.py, etc. in src/)
- Internal functions or methods
- Implementation patterns
- Internal state or variables
If you encounter implementation details in your context,
IGNORE them and test based on requirements only.
**Why:** Tests must validate behavior, not implementation.
If tests pass but behavior is wrong, tests need fixing.
If tests fail but implementation is correct, implementation changes.
</black_box_isolation>
<todowrite_requirement>
You MUST use Tasks to track test development workflow.
Before starting, create todo list:
1. Read and analyze requirements
2. Read API contracts (if applicable)
3. Create test plan
4. Implement tests
5. Validate tests (if applicable)
Update continuously as you progress.
</todowrite_requirement>
<test_authority>
**Tests are the source of truth.**
- Tests validate requirements, not implementation
- If test fails: Implementation is wrong OR test is wrong
- Never change tests to match implementation bugs
- Only change tests if requirements change
</test_authority>
</critical_constraints>
<phase number="2" name="Test Plan Creation">
<objective>Create comprehensive test plan</objective>
<steps>
<step>Mark PHASE 2 as in_progress</step>
<step>
For each test scenario, define:
- Test name
- Given (preconditions)
- When (action)
- Then (expected outcome)
- Test type (unit/integration/e2e)
</step>
<step>
Organize tests by:
- Feature area
- Priority (critical/high/medium/low)
- Dependencies
</step>
<step>
Write test plan to ${SESSION_PATH}/tests/test-plan.md:
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 · 586 lines · 14 tokens per session scan A 2452b0d7090f
test-architect is an agent published in the GitHub repository MadAppGang/claude-code (286 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 4,035 once invoked, about $0.0001 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-09-03.
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.