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.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginnpx agentmods add agents/navraj007in/architecture-cowork-plugin/test-generatorWrote 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.
[](https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/test-generator)<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.
<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>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.00019 | $0.02827 |
| Opus 5 | $0.00010 | $0.01413 |
| Sonnet 5 | $0.00004 | $0.00565 |
| Haiku 4.5 | $0.00002 | $0.00283 |
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.
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/.csfiles insrc_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(orjest.config.json)- testEnvironment: 'node' for backend, 'jsdom' for frontend
- testMatch:
['**/__tests__/**/*.ts', '**/*.test.ts'] - collectCoverageFrom: exclude
.d.tsandindex.ts - coverageThreshold: use passed
coverage_target - moduleNameMapper for path aliases
- Create
tsconfig.test.jsonwithjest,nodetypes
For Python (pytest):
- Create/update
pytest.ini- testpaths:
tests - python_files:
test_*.py *_test.py - addopts:
--verbose --strict-markers
- testpaths:
- Create
conftest.pywith shared fixtures@pytest.fixture def sample_<entity>():- DB setup/teardown if database_approach is 'real'
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.
- 11d ago First seen · 397 lines · 19 tokens per session scan A 5134ce756b95
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.
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.
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…
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".
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
spec-tester
Verifies that implemented tasks actually work. Uses Playwright for UI testing, runs test suites, and only marks Verified: yes after real verification.
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…