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/armoin2018/ai-leyWrote 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/armoin2018/ai-ley/build-unit-tests)<a href="https://agentmods.dev/commands/armoin2018/ai-ley/build-unit-tests"><img src="https://agentmods.dev/badge/commands/armoin2018/ai-ley/build-unit-tests.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.1 | $0.00000 | $0.00131 |
| Opus 5 | $0.00000 | $0.00066 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
build-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 7d 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
build-unit-tests
Generate comprehensive unit testing infrastructure including test configuration, health checks, regression tests, synthetic transactions, coverage dashboards, and CI/CD integration.
Usage
ai-ley build-unit-tests [--mode=plan|dry-run|apply]
Full Documentation
See: .ai-ley/shared/prompts/build-unit-tests.md
This command creates:
- Unit test structure and configuration
- Health check tests for system components
- Regression tests with golden files
- Synthetic transaction journeys
- Test Control API for remote execution
- Coverage dashboards and policies
- Timeout/retry mechanisms
- CI/CD workflow integration
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.
- 7d ago First seen · 25 lines · 0 tokens per session scan A 8bab5007daca
build-unit-tests is a command published in the GitHub repository armoin2018/ai-ley (11 stars, last pushed 7mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 131 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-31.
Other commands, from other repositories
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.