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/penwyp/ClaudePreferenceWrote 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/penwyp/claudepreference/m-test-generation)<a href="https://agentmods.dev/commands/penwyp/claudepreference/m-test-generation"><img src="https://agentmods.dev/badge/commands/penwyp/claudepreference/m-test-generation/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/penwyp/claudepreference/m-test-generation"><img src="https://agentmods.dev/badge/commands/penwyp/claudepreference/m-test-generation.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.00000 | $0.00152 |
| Opus 5.5 | $0.00000 | $0.00061 |
| Sonnet 5.5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
m-test-generation 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
Test Generation Workflow
Test type and target: $ARGUMENTS
If no parameters specified, generate unit tests for recently modified files by default. Format: [test-type] [target] [coverage-goal] Examples: "unit src/auth 90%", "integration api", "e2e user-flow", "all components"
Commands:
-
Analyze code coverage - Identify untested functions and code paths in specified target
-
Generate unit tests - Create comprehensive test cases for individual components
-
Create integration tests - Build tests for component interactions and workflows
-
Run test suite - Execute all tests and verify functionality
-
Update test documentation - Record test coverage and testing strategies
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 · 19 lines · 0 tokens per session scan A df1a47b40205
m-test-generation is a command published in the GitHub repository penwyp/ClaudePreference (136 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 152 tokens. 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
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.