test-generator

test-generator is an agent for Claude Code from navraj007in/architecture-cowork-plugin. It costs 19 tokens per session (2,827 once invoked), scanned A, original, Apache-2.0.

A code-generation agent that creates unit tests for individual parts, integration tests for connected parts, and end-to-end tests for complete user flows.

In plain words
What is it for?
Use it to generate test suites for supported backend components, using the project's chosen test frameworks, database approach, entities, authentication method, and coverage target.
Why use it?
It reduces the manual work of finding source files, understanding project components, and creating tests without overwriting existing test files.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { UserService } from '../user';.

Part of the architect plugin — 48 skills, 63 commands, 19 agents, 7 MCP servers shipped together

Good fit Use it to generate test suites for supported backend components, using the project's chosen test frameworks, database approach, entities, authentication method, and coverage target.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin
agentmods
npx agentmods add agents/navraj007in/architecture-cowork-plugin/test-generator

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/test-generator/github.svg)](https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/test-generator)
Your own site
<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/test-generator"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/test-generator/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-generator

Your own site · 80×15
<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/test-generator"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/test-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,827 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.00019 $0.02827
Opus 5 $0.00010 $0.01413
Sonnet 5 $0.00004 $0.00565
Haiku 4.5 $0.00002 $0.00283

Measured 11d ago against content hash 5134ce756b95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

test-generator 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 11d 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-generator.md · 397 lines

How it starts

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

Test Generator Agent

Autonomous code generation agent that creates test suites per component following the testing-strategy skill.

Input

The /architect:generate-tests command passes:

{
  "components": [
    {
      "name": "api-server",
      "type": "backend",
      "language": "typescript",
      "framework": "express",
      "directory": "/path/to/project/api-server",
      "src_dirs": ["src/services", "src/controllers", "src/middlewares"]
    }
  ],
  "test_config": {
    "coverage_target": 80,
    "unit_framework": "jest",
    "e2e_framework": "playwright",
    "database_approach": "real"
  },
  "entities": [
    { "name": "User", "fields": ["id", "email", "name", "role", "createdAt"] },
    { "name": "Post", "fields": ["id", "title", "content", "authorId", "createdAt"] }
  ],
  "auth_strategy": "jwt",
  "project_stage": "mvp"
}

Process

Step 1: Detect Existing Source Files

For each component, use Glob and Bash to discover:

  • All .ts/.py/.go/.cs files in src_dirs
  • Package/module structure
  • Existing test files (if any) to avoid overwriting
find <component_dir>/src -type f -name "*.ts" | grep -v ".test.ts" | sort

Step 2: Generate Framework Config Files

Per component, create framework-specific config following testing-strategy skill:

For Node.js (Jest):

  • Create/update jest.config.js (or jest.config.json)
    • testEnvironment: 'node' for backend, 'jsdom' for frontend
    • testMatch: ['**/__tests__/**/*.ts', '**/*.test.ts']
    • collectCoverageFrom: exclude .d.ts and index.ts
    • coverageThreshold: use passed coverage_target
    • moduleNameMapper for path aliases
  • Create tsconfig.test.json with jest, node types

For Python (pytest):

  • Create/update pytest.ini
    • testpaths: tests
    • python_files: test_*.py *_test.py
    • addopts: --verbose --strict-markers
  • Create conftest.py with shared fixtures
    • @pytest.fixture def sample_<entity>():
    • DB setup/teardown if database_approach is 'real'

Read the full file on GitHub · 397 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. 11d ago First seen · 397 lines · 19 tokens per session scan A 5134ce756b95

Subscribe to this mod's changes

test-generator is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,827 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-31.

Related

Other agents, from other repositories

coverage-analyst

Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.

sd0xdev/sd0x-harness · 34 tokens

qa-engineer

Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…

KevinZai/commander · 34 tokens

test-strategist

Create comprehensive test strategies for software projects. User says: "Create a test strategy for our e-commerce platform" User says: "What tests should we write for the payment flow?" User says: "Review our test coverage and suggest improvements".

fattain-naime/engineering-docs · 66 tokens

dnp-test-writer

🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.

zdanovichnick/dotnet-pilot · 37 tokens

spec-tester

Verifies that implemented tasks actually work. Uses Playwright for UI testing, runs test suites, and only marks Verified: yes after real verification.

Habib0x0/spec-driven-plugin · 33 tokens

spec-acceptor

Performs user acceptance testing by mapping completed tasks back to requirements and verifying traceability, non-functional requirements, and overall completeness. Produces a UAT report with pass/fail per acceptance criterion and a formal sign-off recommendation. Does NOT re-run functional tests (the spec-tester…

Habib0x0/spec-driven-plugin · 251 tokens