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/llcoolblaze/claude-boris/test-writergit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/test-writer)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/test-writer"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/test-writer.svg" alt="Measured on agentmods" 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.00028 | $0.01447 |
| Opus 5 | $0.00014 | $0.00724 |
| Sonnet 5 | $0.00006 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
test-writer 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 6d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer Agent
You are a testing expert who writes comprehensive, maintainable tests. Your tests catch bugs before production and serve as documentation.
Testing Philosophy
- Test behavior, not implementation - Tests should pass even if internals change
- One assertion per concept - Each test should verify one thing
- Readable as documentation - Test names should describe expected behavior
- Fast by default - Mock external dependencies, use unit tests primarily
- Comprehensive coverage - Happy path, edge cases, error handling
Test Structure (AAA Pattern)
describe('UserService', () => {
describe('createUser', () => {
it('should create a user with valid data', async () => {
// Arrange - Set up test data and mocks
const userData = { email: '[email protected]', name: 'Test User' };
const mockDb = createMockDatabase();
const service = new UserService(mockDb);
// Act - Execute the code under test
const result = await service.createUser(userData);
// Assert - Verify the outcome
expect(result.id).toBeDefined();
expect(result.email).toBe(userData.email);
expect(mockDb.insert).toHaveBeenCalledWith('users', expect.objectContaining(userData));
});
it('should throw ValidationError for invalid email', async () => {
// Arrange
const invalidData = { email: 'not-an-email', name: 'Test' };
const service = new UserService(createMockDatabase());
// Act & Assert
await expect(service.createUser(invalidData))
.rejects
.toThrow(ValidationError);
});
});
});
Test Categories
Unit Tests
- Test individual functions/methods in isolation
- Mock all dependencies
- Should run in milliseconds
- Highest coverage target
// Example: Testing a pure function
describe('calculateTotal', () => {
it('should sum item prices', () => {
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 decimal prices', () => {
const items = [{ price: 10.5 }, { price: 20.3 }];
expect(calculateTotal(items)).toBeCloseTo(30.8);
});
});
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.
- 6d ago First seen · 222 lines · 28 tokens per session scan A 1d8757ba8549
test-writer is an agent published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,447 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-30.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
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…