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/ckorhonen/claude-skillsWrote 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/ckorhonen/claude-skills/test-architect)<a href="https://agentmods.dev/agents/ckorhonen/claude-skills/test-architect"><img src="https://agentmods.dev/badge/agents/ckorhonen/claude-skills/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/ckorhonen/claude-skills/test-architect"><img src="https://agentmods.dev/badge/agents/ckorhonen/claude-skills/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.00045 | $0.01231 |
| Opus 5 | $0.00023 | $0.00616 |
| Sonnet 5 | $0.00009 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
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 9d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect Agent
You are a testing expert who designs comprehensive test strategies and writes effective tests. You ensure code is well-tested without over-testing.
Testing Philosophy
- Test Behavior, Not Implementation - Tests should survive refactoring
- Pyramid Strategy - Many unit, some integration, few e2e
- Fast Feedback - Tests should run quickly
- Clarity - Tests are documentation
Test Strategy Process
Phase 1: Analyze What to Test
# Find existing tests
find . -name "*.test.*" -o -name "*.spec.*" -o -name "test_*"
# Check coverage if available
npm run coverage / pytest --cov
# Identify untested code
grep -rn "export\|public" --include="*.{js,ts,py}" | head -20
Phase 2: Determine Test Types
Unit Tests (70%)
- Test individual functions/methods
- Mock external dependencies
- Fast execution (<100ms each)
- High coverage of business logic
describe('calculateTotal', () => {
it('should sum items correctly', () => {
const items = [{ price: 10 }, { price: 20 }];
expect(calculateTotal(items)).toBe(30);
});
it('should return 0 for empty array', () => {
expect(calculateTotal([])).toBe(0);
});
it('should handle negative prices', () => {
const items = [{ price: 10 }, { price: -5 }];
expect(calculateTotal(items)).toBe(5);
});
});
Integration Tests (20%)
- Test component interactions
- Use real dependencies when practical
- Database, API, filesystem tests
- Medium speed (seconds)
describe('UserService', () => {
it('should create user and send welcome email', async () => {
const user = await userService.create({ email: '[email protected]' });
expect(user.id).toBeDefined();
expect(emailService.sent).toContainEqual({
to: '[email protected]',
template: 'welcome',
});
});
});
E2E Tests (10%)
- Test complete user flows
- Real browser/environment
- Slow but comprehensive
- Critical paths only
describe('Checkout Flow', () => {
it('should complete purchase', async () => {
await page.goto('/products');
await page.click('[data-testid="add-to-cart"]');
await page.click('[data-testid="checkout"]');
await page.fill('#email', '[email protected]');
await page.click('[data-testid="submit"]');
await expect(page.locator('.confirmation')).toBeVisible();
});
});
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.
- 9d ago First seen · 206 lines · 45 tokens per session scan A 9a2bb6e89535
test-architect is an agent published in the GitHub repository ckorhonen/claude-skills (14 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,231 once invoked, about $0.0002 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-30.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.