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/sigistry/marketplaceWrote 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/sigistry/marketplace/generate-unit-tests)<a href="https://agentmods.dev/commands/sigistry/marketplace/generate-unit-tests"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/generate-unit-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/sigistry/marketplace/generate-unit-tests"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/generate-unit-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.00018 | $0.03033 |
| Opus 5 | $0.00009 | $0.01517 |
| Sonnet 5 | $0.00004 | $0.00607 |
| Haiku 4.5 | $0.00002 | $0.00303 |
Grade A, and why
generate-unit-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 5d 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Generation Command
You are tasked with generating comprehensive, production-quality unit tests for the specified code. Follow these steps precisely to create thorough test coverage:
Step 1: Identify Target Code
If the user provided a file path or function name:
- Locate and read the specified file(s) or function(s)
- If a directory is specified, recursively find all testable code files within it
- Identify all public functions, classes, and methods that need testing
If no specific target is provided:
- Ask the user which file, function, or class they want tested
- Provide a list of recently modified files as suggestions
- Show files with low or no test coverage if available
Step 2: Analyze the Code
For each target function or class, perform thorough analysis:
Function Analysis
- Purpose: What does this function do?
- Input Parameters: Types, valid ranges, constraints, optional vs required
- Return Values: What does it return? What are possible return values?
- Side Effects: Does it modify state, make API calls, write to DB, etc.?
- Dependencies: What external modules or services does it depend on?
- Error Conditions: What errors can it throw? Under what conditions?
- Edge Cases: Boundary values, null/undefined, empty collections, special characters
- Business Logic: What business rules does it implement?
Class Analysis
- Responsibilities: What is this class responsible for?
- Public Methods: All methods that need testing
- State Management: How does internal state change?
- Dependencies: What dependencies are injected or used?
- Lifecycle: Constructor, initialization, cleanup
- Inheritance: Parent classes and their behavior
Step 3: Detect Testing Framework
Automatically detect the testing framework from the project:
JavaScript/TypeScript
- Check
package.jsonfor: jest, vitest, mocha, jasmine - Default to Jest if not specified
- Check for existing test files to match their style
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.
- 5d ago First seen · 490 lines · 18 tokens per session scan A 512c56bf111b
generate-unit-tests is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 3,033 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 commands, from other repositories
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
octo-debug
Debug a symptom through reproducible, bounded evidence.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
verify
Verify a repository in fast or full mode with runner-first execution, deterministic stage order, and explicit PASS/FAIL/SKIP output.