agentmods.dev

test-writer

test-writer is a skill for Claude Code from RealDougEubanks/ClaudeMarketplace. It costs 32 tokens per session (1,398 once invoked), scanned A, original, MIT.

A test-generation tool that writes unit tests for individual pieces of code and integration tests for interactions between pieces. It detects the project's existing test framework and style.

In plain words
What is it for?
Use it for a file or function to create tests for public behaviour, including needed mocks for dependencies, using frameworks such as Jest, Vitest, pytest, Go test, or PHPUnit when detected.
Why use it?
It reduces the manual effort of deciding what to test and how to match the project's testing conventions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the test-writer plugin — 1 skill shipped together

not rated 1repo today A scan 32 tokens original MIT

Good fit Use it for a file or function to create tests for public behaviour, including needed mocks for dependencies, using frameworks such as Jest, Vitest, pytest, Go test, or PHPUnit when detected.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/realdougeubanks/claudemarketplace/test-writer
View source ↗ RealDougEubanks/ClaudeMarketplace
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.

Any agent
npx skills add RealDougEubanks/ClaudeMarketplace --skill test-writer
Clone the repo
git clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplace

Made for: Claude Code.

Or install test-writer, the plugin that ships this one along with the rest of its 1 skill.

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.

agentmods badge for test-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/test-writer/github.svg)](https://agentmods.dev/skills/realdougeubanks/claudemarketplace/test-writer)
Your own site
<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/test-writer"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/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.

agentmods 80×15 button for test-writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/test-writer"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/test-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,398 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01398
Opus 5 $0.00016 $0.00699
Sonnet 5 $0.00006 $0.00280
Haiku 4.5 $0.00003 $0.00140

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

skills/test-writer/SKILL.md · 103 lines

How it starts

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

Test Writer

Generate comprehensive unit and integration tests for a given file or function, auto-detecting the project test framework and matching the existing test style.

Instructions

When invoked via /test-writer:

  1. Identify the target. Ask the user: which file or function should tests be written for? Accept:

    • An absolute or relative file path (e.g. src/utils/parser.ts)
    • A function or method name (ask which file it lives in if ambiguous)

  2. Read the target file using Read. Understand:

    • All exported/public functions, classes, and methods
    • Their parameter types, return types, and documented or inferred behavior
    • Dependencies (imports/requires) that will need to be mocked

  3. Detect the test framework using Glob and Read:

    • Jest: look for jest.config.*, or "jest" key in package.json
    • Vitest: look for vitest.config.*, or "vitest" in package.json devDependencies
    • pytest: look for pytest.ini, pyproject.toml containing [tool.pytest.ini_options], or conftest.py
    • Go test: look for go.mod and any existing *_test.go files
    • PHPUnit: look for phpunit.xml or phpunit.xml.dist, or phpunit/phpunit in composer.json
    • Mocha: look for .mocharc.*, or "mocha" in package.json devDependencies
    • RSpec: look for .rspec, spec/spec_helper.rb, or rspec in Gemfile
    • JUnit: look for junit in pom.xml or build.gradle/build.gradle.kts
    • xUnit / NUnit / MSTest: look for xunit, NUnit, or MSTest package references in *.csproj
    • If multiple are present, ask the user which to use.

  4. Match existing test style. Use Glob to find existing test files matching **/*.test.*, **/*.spec.*, **/*_test.*, or tests/**/*. Read 1–2 representative test files to capture:

    • Describe/context block structure
    • Assertion library and style (expect, assert, should)
    • How mocks, stubs, and fixtures are set up
    • Import paths and module resolution patterns

Read the full file on GitHub · 103 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 103 lines · 32 tokens per session scan A d0afe30a8dad

Subscribe to this mod's changes

test-writer is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,398 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-31.

Claude CodeTestingUnit testingclaudeclaude-aiclaude-code-pluginclaude-code-skillclaude-code-skills
Related

Other skills, from other repositories

tools-unity-test-framework

Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.

IdoCohen560/claude-unity-game-studio · 27 tokens

test-helpers

Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

IdoCohen560/claude-unity-game-studio · 50 tokens

unity-testing

Unity 6 testing guide. Use when writing unit tests, integration tests, or doing TDD with Unity Test Framework. Covers Edit Mode and Play Mode tests, NUnit attributes ([Test], [UnityTest], [SetUp], [TearDown]), testing MonoBehaviours and coroutines, and CI/CD integration. Based on Unity 6.3 LTS documentation.

IdoCohen560/claude-unity-game-studio · 78 tokens

uw-unity-test-runner

Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode…

IdoCohen560/claude-unity-game-studio · 136 tokens

plan-qa

Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…

foyzulkarim/skills · 110 tokens

execute-qa

Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…

foyzulkarim/skills · 106 tokens