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/cveralyon/axel-setup/test-gengit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/test-gen)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/test-gen"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/test-gen.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.00019 | $0.00430 |
| Opus 5 | $0.00010 | $0.00215 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
test-gen 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 3d 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.
What it actually says
Generate thorough test specs for a given file, feature, or bug fix.
Step 1: Analyze the target
- Read the file(s) to test
- Identify: public methods, input variations, dependencies, side effects, error paths
- Check existing specs for patterns:
ls spec/or search for similar test files
Step 2: Plan test cases
For each public method/endpoint/component:
- Happy path — normal expected usage
- Edge cases — empty inputs, nil/null, boundary values, large datasets, special characters
- Error cases — invalid inputs, missing associations, unauthorized access, network failures
- State transitions — if AASM states involved, test each valid transition and reject invalid ones
- Authorization — if Pundit policies, test each role (admin, manager, recruiter, freelance)
Step 3: Generate specs
Rails (RSpec):
- Model specs: validations, associations, scopes, instance methods
- Request specs: HTTP status, response body, side effects (DB changes, jobs enqueued)
- Service specs: input/output, error handling, external service mocking
- Follow
describe/context/itnesting. Uselet/let!for setup - Use
FactoryBotif factories exist, otherwisebuild/createdirectly
Next.js (when Vitest is set up):
- Component tests: renders correctly, user interactions, loading/error states
- Hook tests: query behavior, mutation side effects, cache invalidation
- Use accessible queries:
getByRole,getByText,getByLabelText
Step 4: Run and verify
- Run the generated specs
- Fix any failures from incorrect assumptions
- Report coverage: what's tested, what's intentionally skipped and why
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.
- 3d ago First seen · 40 lines · 19 tokens per session scan A c07925ecb267
test-gen is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 430 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
syllago-author
/home/hhewett/.local/src/syllago/content/agents/syllago-author/AGENT.md.
feature-flow
Build, test, verify, and review an already planned feature. Operates on a feature branch off trunk; prepares a PR but does not merge.
review
Review PR and build output for quality, security, and compliance. Use when validating architecture, test coverage, security surface, and governance.
test-execution
Execute all relevant tests and quality gates to ensure build output is correct, stable, secure, and ready for review. This is feature-flow's Phase 3 (and Phase 3.5 for live-system verification) — local, pre-push verification. Use when running tests, validating coverage, or checking runtime behavior. Distinct from the…
design
Convert the specification into a clear, actionable technical design with architecture, components, interfaces, and data flows. Use when translating requirements into a buildable system design.
learn
Product retrospective agent. Runs after a release, after a measure agent anomaly flag, or at end of sprint. Maps findings to DORA AI capabilities and produces plan agent action items. Distinct from fawkes learn.md which handles platform incident postmortems.