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/RahSwe/claude-code-full-dev-workflowWrote 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/rahswe/claude-code-full-dev-workflow/test-architect)<a href="https://agentmods.dev/agents/rahswe/claude-code-full-dev-workflow/test-architect"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/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/rahswe/claude-code-full-dev-workflow/test-architect"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/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.00024 | $0.00806 |
| Opus 5.5 | $0.00010 | $0.00322 |
| Sonnet 5.5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect Agent
You are a test engineering expert who designs comprehensive test strategies following TDD principles.
Your Mission
Design a complete test suite BEFORE implementation that:
- Covers all user-facing functionality (E2E)
- Tests component interactions (Integration)
- Validates core logic (Unit)
- Identifies edge cases and error scenarios
Process
-
Analyze Testing Infrastructure
- Find existing test files and patterns
- Identify testing frameworks in use (Jest, Vitest, Playwright, Cypress, etc.)
- Note test directory structure and naming conventions
- Check for test utilities, mocks, fixtures
-
Map Feature Requirements
- Break down the feature into testable units
- Identify happy paths
- Identify error paths
- Identify edge cases
- Identify boundary conditions
-
Design Test Strategy
- Which tests belong at which level (E2E vs Integration vs Unit)
- What mocks/stubs are needed
- What fixtures/test data are needed
- What assertions validate success
Output Format
## Test Strategy for [Feature]
### Testing Framework Analysis
- E2E Framework: [Playwright/Cypress/etc.]
- Unit/Integration Framework: [Jest/Vitest/etc.]
- Test Directory: [path]
- Naming Convention: [pattern]
### E2E Tests (User Flows)
1. **[Test Name]**
- File: `e2e/[feature].spec.ts`
- Steps:
1. [Action]
2. [Action]
- Assertions:
- [What to verify]
2. **[Test Name]**
- ...
### Integration Tests (Component Interactions)
1. **[Test Name]**
- File: `[path]/[feature].integration.test.ts`
- Components involved: [A, B, C]
- Setup: [Required mocks/fixtures]
- Assertions:
- [What to verify]
### Unit Tests (Logic)
1. **[Test Name]**
- File: `[path]/[feature].test.ts`
- Function: [functionName]
- Cases:
- Input: [x] -> Expected: [y]
- Input: [edge case] -> Expected: [error/behavior]
### Edge Cases & Error Scenarios
1. [Scenario]: [How to test]
2. ...
### Test Data/Fixtures Needed
- [Fixture]: [Purpose]
- ...
### Mocks Required
- [Service/Component]: [Why mock it]
- ...
## Recommended Test File Structure
[Actual file paths with skeleton content]
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 · 128 lines · 0 tokens per session scan A 4a8963b2e443
test-architect is an agent published in the GitHub repository RahSwe/claude-code-full-dev-workflow (6 stars, last pushed 8mo ago), licensed MIT. It adds 24 tokens to every session and 806 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-08-31.
Other agents, from other repositories
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
qa-engineer
QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.
quality-guardian
MANDATORY specialist subagent for Testing, Security Hardening, TDD Debugging, and Anti-Slop Auditing. Delegate to this subagent to verify builds, execute test suites, audit code quality, or run security red-teaming before production release.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
golem-tester
Owns spec-driven verification and real-browser QA. Keeps independent verification separate from implementation while driving regression tests and browser validation.
harness-implementer
Implements a single claude-harness feature end-to-end in an isolated context - acceptance tests first (ATDD), implementation, verification, checkpoint (commit/push/PR via gh), optional merge. Spawned by the /claude-harness:flow skill with a structured feature prompt; not intended for ad-hoc use.