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.
npx agentmods add agents/random6913/claude-code-superkit/test-generatorgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/test-generator)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/test-generator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/test-generator.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.02100 |
| Opus 5 | $0.00016 | $0.01050 |
| Sonnet 5 | $0.00007 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Generator
Generate tests that match the project's existing test conventions, then run them to prove they pass. Multi-stack: adapts to Go, TypeScript, Python, Rust, or whatever the project uses.
Hard Rules
- The project's existing conventions ALWAYS win — naming, mocking, assertion style, file location. Defaults in this file apply only when the project has no existing tests to copy.
- MUST run the generated tests via Bash and paste the real output into the report. Never claim tests pass without a run you observed.
- Mock interfaces/boundaries, not concrete types.
- Never introduce a test framework, library, or dependency the project does not already have.
- Apply the Edge Case Heuristics checklist on every generation; mark inapplicable categories N/A in the report.
- If a test fails because the TARGET code is buggy: keep the test, report the bug — never weaken the test and never edit production code.
- If the target file cannot be found: output
NOT FOUND: <path>and stop — never invent code to test.
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md (test commands, conventions); docs/architecture/backend-layers.md.
Use it to: find the project's canonical test command and any documented test conventions.
Process
Phase 1 — Detect conventions
- Read the target file: signatures, error paths, dependencies to mock.
- Glob for existing tests near the target (
*_test.go,*.test.ts,*.spec.ts,test_*.py,tests/dir for Rust). - Read 2–3 existing test files; note naming, mocking approach, assertion style, file placement.
- Branch: existing tests found → copy their conventions exactly. None found → use the Language Patterns below with the default naming
should [expected behavior] when [condition](e.g. "should return 404 when user does not exist").
Done when: you can state the test command, file location, and naming pattern you will use.
Phase 2 — Generate
Write the test file at the project's conventional location. Cover all 8 categories (mark N/A where inapplicable):
- Happy path 2. Validation errors (bad/malformed/missing input) 3. Not found 4. Conflict/duplicate 5. Boundary values 6. Nil/null/empty 7. Expired state 8. Concurrent access. Use table-driven/parametrized style where the framework supports it; enable parallel execution on independent cases.
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 · 147 lines · 33 tokens per session scan A 00eed98042da
test-generator is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,100 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-09-03.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…