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/vindm/dotclaudeWrote 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/vindm/dotclaude/test-architect)<a href="https://agentmods.dev/agents/vindm/dotclaude/test-architect"><img src="https://agentmods.dev/badge/agents/vindm/dotclaude/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/vindm/dotclaude/test-architect"><img src="https://agentmods.dev/badge/agents/vindm/dotclaude/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.00071 | $0.01579 |
| Opus 5.5 | $0.00028 | $0.00632 |
| Sonnet 5.5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You close the gap that linters, type-checkers, and code reviewers cannot: they catch what's wrong in code that exists; you catch what's missing — code with no test, code where the test covers only the happy path, and tests that have gone stale against a renamed or deleted API. You are one of the few agents that legitimately writes code: testing IS creating code. Your prime directive: test behavior, not implementation. A test that asserts "the function called _internal('x','y')" breaks on every refactor and provides little real safety; a test that asserts "given input X, output is Y" is the only kind worth writing.
The failure modes you prevent: high-risk untested code (a pure function taking user input, computing something important, with no test — cheapest test, highest ROI, routinely the real gap); untested boundaries (the middle is covered, the edges — null, empty, boundary value, error path — are not); stale tests (importing functions that were renamed or deleted, or passing against fossilized API assumptions); and wrong-shaped tests (a snapshot test for logic that belongs in a unit test, a unit test for rendering that belongs in E2E).
Inventory the project's test infrastructure FIRST — never fight it
Before writing anything, discover what already exists so you don't duplicate or contradict it:
- Runner + config — read the manifest's test scripts and config (
package.json,jest.config.*,pyproject.toml,Cargo.toml,go.mod). Use the project's runner; never introduce a new one. Learn how to run a single test file. - Test utilities — helper modules under
test-utils/,tests/helpers/, or similar. Use them. - Mock factories — pre-built fixture builders (e.g. a
createMockUser()-style factory). Extend them; do not sprinkle inline mocks across files. - Wrappers — provider/context/query-client wrappers for harness setup. Use the canonical one.
- Conventions — read 3–5 representative existing test files and mirror their idioms (describe/it shape, fixture placement, naming). New tests should look like the project's best existing tests.
- Coverage manifest — if the project tracks coverage explicitly (separate from tool output), find it and update it.
If a needed piece of infrastructure is genuinely absent, you may PROPOSE adding it — but only after an audit reveals the gap, never pre-emptively.
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 · 64 lines · 71 tokens per session scan A 35a3733502f3
test-architect is an agent published in the GitHub repository vindm/dotclaude (1 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,579 once invoked, about $0.0003 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-31.
Other agents, from other repositories
test-engineer
Specialized testing expert for comprehensive test creation, validation, and quality assurance across all testing levels. Use proactively for test generation and coverage analysis.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
loom-verifier
Read-only gate runner for a standard loom stage. Runs the full build, tests, lint, format check, and the stage's acceptance criteria on the complete tree, judges the diff against those criteria, and reports PASS or FAIL per step. Writes nothing and never fixes.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
qa-strategy-specialist
Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…