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 commands/4tyone/snek/snek.test.generategit clone --depth 1 https://github.com/4tyone/snekWrote 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/4tyone/snek/snek.test.generate)<a href="https://agentmods.dev/commands/4tyone/snek/snek.test.generate"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.test.generate.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.00007 | $0.00226 |
| Opus 5 | $0.00003 | $0.00113 |
| Sonnet 5 | $0.00001 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
snek.test.generate 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.
What it actually says
Generate Tests
Generate unit tests for a function or module.
Usage
User provides:
- File path
- Function name (optional - if not provided, generate tests for all public functions)
Steps
- Get file outline:
.snek/scripts/get-file-outline.sh "/path/to/file"
-
Read the function(s) to understand:
- Input parameters and types
- Return type
- Edge cases
- Error conditions
-
Generate tests covering:
- Happy path (normal operation)
- Edge cases (empty input, boundary values)
- Error cases (invalid input, error conditions)
-
Format tests for the language:
- Rust:
#[test]functions - Python: pytest functions
- JavaScript/TypeScript: Jest/Mocha tests
- Go:
func TestXxxfunctions
- Rust:
-
Present tests to user. If approved, write to appropriate test file location.
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 · 42 lines · 7 tokens per session scan A ca01ed0234d5
snek.test.generate is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 226 once invoked, about $0.0000 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 commands, from other repositories
unity-test
Writes missing tests and runs them via MCP. Identifies untested code, creates EditMode/PlayMode tests, executes via runtests, reports results.
gen-tests
Wraps agents/test-class-generator/AGENT.md. Takes a target Apex class, produces a test class targeting ≥ 85% coverage using the canonical factories in templates/apex/tests/.
refactor-apex
Wraps agents/apex-refactorer/AGENT.md. Takes a target class, returns a refactored version + test class using templates/apex/.
test-unit-agora
编译并运行当前任务相关的单元测试，输出结果并分析失败原因.
pipeline
Execute predefined pipelines for common development workflows.
testing
Comprehensive testing through distributed execution.