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.
npx agentmods add agents/rahswe/claude-code-full-dev-workflow/test-architectgit clone --depth 1 https://github.com/RahSwe/claude-code-full-dev-workflowWhat 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 | $0.00024 | $0.00806 |
| Opus 5 | $0.00012 | $0.00403 |
| Sonnet 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 2d 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.
- 2d 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 7mo ago), licensed MIT. It adds 24 tokens to every session and 806 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.