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.
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/commands/florianbruniaux/claude-code-plugins/generate-tests)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/generate-tests"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/generate-tests/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/commands/florianbruniaux/claude-code-plugins/generate-tests"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/generate-tests.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.00009 | $0.00447 |
| Opus 5.5 | $0.00004 | $0.00179 |
| Sonnet 5.5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
generate-tests 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 1mo 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 Tests
Generate comprehensive tests for specified code.
Instructions
- Read the target file(s)
- Identify testable units (functions, classes, methods)
- Generate tests following project conventions
- Ensure high coverage of edge cases
Test Generation Process
1. Analyze Target
- Identify public interfaces
- Understand dependencies
- Note edge cases and boundaries
2. Detect Test Framework
Check for:
jest.config.js→ Jestvitest.config.ts→ Vitestpytest.ini→ pytestmochain package.json → Mocha
3. Generate Tests
Follow the detected framework conventions.
Test Categories
Happy Path
Normal expected behavior with valid input.
Edge Cases
- Empty inputs
- Null/undefined values
- Boundary values (0, -1, MAX_INT)
- Single item vs multiple items
Error Cases
- Invalid input types
- Missing required parameters
- Network/IO failures
- Timeout scenarios
Integration Points
- Database interactions
- External API calls
- File system operations
Output Format
describe('[ComponentName]', () => {
describe('[methodName]', () => {
// Happy path
it('should [expected behavior] when [condition]', () => {
// Arrange
// Act
// Assert
});
// Edge cases
it('should handle empty input', () => {});
it('should handle null values', () => {});
// Error cases
it('should throw when [invalid condition]', () => {});
});
});
Conventions
- One assertion per test (when practical)
- Descriptive test names
- AAA pattern (Arrange-Act-Assert)
- No test interdependence
- Mock external dependencies
Usage
/generate-tests src/utils/calculator.ts
/generate-tests src/services/
$ARGUMENTS
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.
- 1mo ago First seen · 95 lines · 9 tokens per session scan A 41a6f88be0b0
generate-tests is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 447 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
a11y-audit
Web accessibility (WCAG 2.1) audit command. axe-core-based checks via PageSpeed Insights.
api-test
HTTP API endpoint testing. Send GET/POST/PUT/DELETE requests, analyze status + response, assertions.
refactor
Refactoring command. Detects code smells and creates a safe refactoring plan.
prompt-test
Regression test for slash command and agent files. Format and content validation.
qa
QA sign-off command. Verifies a change against acceptance criteria, runs the test suite, probes edge cases, and issues a ship / no-ship verdict via the qa-lead agent.
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.