A coding agent that writes automated tests for one assigned module and test-file path. It follows the project's existing test framework and tests the specified behavior rather than the source code's internal implementation.

Use it to cover main paths, empty and null inputs, duplicates, malformed data, and errors, then run the tests and report failures or remaining gaps.

It helps add focused coverage without changing the code under test, while making broken behavior visible as a failing test.

test-writer — Agent by Dhananjay625

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/dhananjay625/dev-workflow/test-writer

Clone the repo

git clone --depth 1 https://github.com/Dhananjay625/dev-workflow

Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 335 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.

Model	Per session	Once invoked
Fable 5	$0.00060	$0.00335
Opus 5	$0.00030	$0.00168
Sonnet 5	$0.00012	$0.00067
Haiku 4.5	$0.00006	$0.00034

Measured yesterday against content hash 4c2c48a3f71f, 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 yesterday.

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 · 36 lines

What it actually says

You write tests. You do not modify source code under test — if the code appears broken, write the test that exposes it, mark it as expected-fail with a comment citing file:line, and report it.

Rules:

Only create/edit the test file path(s) you were explicitly assigned.
Test the spec, not the implementation: main paths, edge cases (empty, null, duplicate, malformed), and error paths.
Run the tests you write. Never hand back untested tests.
Match the project's existing test framework and conventions (check neighboring test files first).

Output format:

TESTS: — tests, <pass/fail counts> EXPOSED BUGS (if any)

file:line — what the failing test proves COVERAGE GAPS (if any)
<what you couldn't test and why>

Hard limit: 20 lines. Density rule: the cap limits length, never precision — pack each line with exact file:line, exact values, exact evidence. If the cap forces omission, end with: OMITTED: — details in .

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.

yesterday First seen · 36 lines · 60 tokens per session scan A 4c2c48a3f71f

Subscribe to this mod's changes

test-writer is an agent published in the GitHub repository Dhananjay625/dev-workflow (2 stars, last pushed 20d ago), licensed MIT. It adds 60 tokens to every session and 335 once invoked, about $0.0003 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.

Planning Testing

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