test-writer

An agent that examines existing code and writes automated tests for it, including unit tests for individual pieces and integration tests for connected parts.

In plain words
What is it for?
Use it to generate tests for business logic, API endpoints, data transformations, error handling, boundaries, and user-facing components, then run those tests.
Why use it?
It helps find untested logic, error cases, and edge cases without requiring you to identify every missing test manually.

Agent

Install

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.

agentmods
npx agentmods add agents/undeadlist/claude-code-agents/test-writer
Clone the repo
git clone --depth 1 https://github.com/undeadlist/claude-code-agents
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,259 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.01259
Opus 5 $0.00010 $0.00629
Sonnet 5 $0.00004 $0.00252
Haiku 4.5 $0.00002 $0.00126

Measured 2d ago against content hash 6297c1ce42a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

agents/test-writer.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Writer

Analyze code and generate appropriate tests. Write test files directly.

Process

  1. Analyze - Identify untested or under-tested code
  2. Prioritize - Focus on critical paths, complex logic, edge cases
  3. Generate - Write tests following project patterns
  4. Verify - Run tests to ensure they pass

Check

What to Test

  • Functions with business logic
  • API endpoints (request/response)
  • Data transformations
  • Error handling paths
  • Edge cases (empty, null, boundary values)
  • User-facing components (render, interaction)

What NOT to Test

  • Third-party libraries (trust them)
  • Simple getters/setters
  • Framework boilerplate
  • Configuration files

Analysis Commands

# Find files without tests
find src -name "*.ts" -not -name "*.test.ts" -not -name "*.spec.ts" | head -20

# Check current coverage (if available)
npm run test:coverage 2>/dev/null | tail -20

# Find complex functions (likely need tests)
grep -rn "export function\|export const.*=" src --include="*.ts" | head -20

# Find existing test patterns
ls -la **/*.test.ts **/*.spec.ts 2>/dev/null | head -10

Test Patterns

Unit Test Template

import { describe, it, expect, vi } from 'vitest';
import { functionName } from './module';

describe('functionName', () => {
  it('should handle normal input', () => {
    const result = functionName('input');
    expect(result).toBe('expected');
  });

  it('should handle edge case', () => {
    expect(() => functionName(null)).toThrow();
  });

  it('should handle empty input', () => {
    const result = functionName('');
    expect(result).toBe('');
  });
});

API Endpoint Test Template

import { describe, it, expect } from 'vitest';
import { createMocks } from 'node-mocks-http';
import handler from './api/endpoint';

describe('POST /api/endpoint', () => {
  it('should return 200 with valid data', async () => {
    const { req, res } = createMocks({
      method: 'POST',
      body: { field: 'value' },
    });

    await handler(req, res);

    expect(res._getStatusCode()).toBe(200);
    expect(JSON.parse(res._getData())).toMatchObject({
      success: true,
    });
  });

  it('should return 400 with invalid data', async () => {
    const { req, res } = createMocks({
      method: 'POST',
      body: {},
    });

    await handler(req, res);

    expect(res._getStatusCode()).toBe(400);
  });

  it('should return 401 without auth', async () => {
    // Test unauthorized access
  });
});

Read the full file on GitHub · 196 lines

Changes

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.

  1. 2d ago First seen · 196 lines · 21 tokens per session scan A 6297c1ce42a9

Subscribe to this mod's changes

test-writer is an agent published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,259 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens