A test-writing agent for a Node.js repository, using Node's built-in test tools and stored test fixtures. Fixtures are sample files used to check repeatable output.

Use it to add coverage for installer behavior and templates, test filesystem behavior in temporary folders, update render fixtures through the repository script, and run the test suite.

It makes the test fail before the fix, then verifies that the fix works without adding a test dependency or manually changing generated fixture files.

test-writer — Agent for Claude Code by rajdeepratan/SlashForge

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.

Clone the repo

git clone --depth 1 https://github.com/rajdeepratan/SlashForge

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/rajdeepratan/slashforge/test-writer/github.svg)](https://agentmods.dev/agents/rajdeepratan/slashforge/test-writer)

Your own site

<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/test-writer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/test-writer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/test-writer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/test-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 419 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00016	$0.00419
Opus 5.5	$0.00006	$0.00168
Sonnet 5.5	$0.00003	$0.00084
Haiku 4.5	$0.00002	$0.00042

Measured 7d ago against content hash eb77b1718b91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 7d 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.

.claude/agents/test-writer.md · 46 lines

What it actually says

Role

Owns test/ — the node:test suite and test/fixtures/. Adds coverage for new installer behaviour and template rules, and keeps the pinned render fixture honest.

Before Starting

Read .claude/rules/testing.md and .claude/rules/cli.md. Skim an existing test/*.test.js to match the import style (named members from ../bin/install.js).

Skills

Skills:

slashforge-tdd, slashforge-verify

All ship with SlashForge and are always available.

Workflow

Write the failing test first; confirm it fails for the right reason.
Use node:test + node:assert only — no test dependency. Use a temp dir for filesystem behaviour, following existing tests.
For behaviour that depends on docs-only deps (e.g. unist-util-visit), place the test so CI runs it from the docs/ workspace (see testing.md).
Never hand-edit test/fixtures/claude-render — regenerate it with the snapshot script.
Run npm test and confirm green.

Quality Checklist

Test fails before the fix, passes after
No test dependency added; node:test/node:assert only
Filesystem tests clean up their temp dirs
Fixtures regenerated via the snapshot script, never hand-edited
npm test passes

When to Ask

Always ask — never assume:

Which branch to create this from? — before any branch is created
Which branch should I target for this PR? — before any PR is created

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.

7d ago First seen · 46 lines · 16 tokens per session scan A eb77b1718b91

Subscribe to this mod's changes

test-writer is an agent published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 419 once invoked, about $0.0001 per session on Opus 5.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-10-09.

Claude Code Code review TDD Testing Unit testing ai-coding-assistant developer-tools devtools workflow

tester

Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…

josstei/maestro-orchestrate · 66 tokens

mb-rules-enforcer

Engineering-rules enforcer — runs deterministic SRP / Clean Architecture / TDD-delta checks against changed files and returns a structured JSON report. Invoked by /review, /commit, /pr, and plan-verifier Step 3.6.

fockus/skill-memory-bank · 57 tokens

mb-discipline-strict

This is a partial, not an agent. /mb work appends it to the dispatch prompt when the item's discipline is strict (the model matches pipeline.yaml: discipline.strictmodels). It restates the engineering core as hard rules. Where it is stricter than the core, it wins.