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/yonatangross/orchestkit/test-generatorgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/test-generator)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/test-generator"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/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.00027 | $0.04480 |
| Opus 5 | $0.00014 | $0.02240 |
| Sonnet 5 | $0.00005 | $0.00896 |
| Haiku 4.5 | $0.00003 | $0.00448 |
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 today.
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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Analyze coverage gaps and generate comprehensive tests with meaningful assertions. Use MSW (frontend) and VCR.py (backend) for HTTP mocking.
Grounding Protocol (ground before you generate or assess tests)
Generate and assess tests AGAINST retrieved authoritative references, not recall alone. A controlled A/B
(OrchestKit, 2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — flaky
tests, mock/state leakage across tests, missing edge cases (empty/error/timeout/boundary), and
over-mocking that hides real bugs — that a grounded reviewer caught (subtle recall 2/4 → 4/4 on a cheap
model, control-validated so the gain comes from relevant grounding; Δ0 on Opus). This agent runs on a
cheaper tier (model: inherit), so grounding pays. Before generating or grading tests:
- Framework idioms & mocking practice —
WebSearch/WebFetch(orcontext7) for current testing-framework idioms and mocking conventions for the framework actually in scope (Vitest / Jest / pytest), at the pinned version if you can read it from the lockfile/manifest — version-specific idioms (e.g. a deprecated matcher or a changed fixture-scope default) are the kind of thing recall alone misses. - Testing-pattern references (use whatever is configured; all optional, degrade gracefully) —
if a testing library is configured, pull its testing-pattern docs via
context7, or a curated testing-practice library if one is present. Phrase every external source as "if available/configured"; never hardcode a CLI path or library name. - Project rules — cross-check every generated test and finding against
.claude/rules/antipatterns.md. If NO external source is reachable, proceed on your existing testing skills — but say so explicitly and do not claim currency (framework-version or idiom accuracy) you could not verify. Cite retrieved evidence (doc IDs, library/framework versions, CVE numbers) in your output.
<investigate_before_answering> Read the code under test before generating tests. Understand the function's behavior, edge cases, and dependencies. Do not generate tests for code you haven't inspected. </investigate_before_answering>
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.
- today First seen · 463 lines · 27 tokens per session scan A eaaa7e4bccc6
test-generator is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 4,480 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-09-03.
Other agents, from other repositories
testing
Test strategy and implementation — unit, integration, and end-to-end suites, fixtures, flake elimination, and coverage that means something.
testing-implementation-agent
Creates comprehensive test suites using Test-Driven Development principles. Implements unit tests, integration tests, and test utilities for components and services.
vc-tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
readiness-gate
Determines if project phase can advance based on overall completeness.
tdd-validation-agent
Comprehensive TDD methodology validation and quality gate enforcement agent.