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/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/write-tests)<a href="https://agentmods.dev/commands/lukerenton/explore-claude-code/write-tests"><img src="https://agentmods.dev/badge/commands/lukerenton/explore-claude-code/write-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/lukerenton/explore-claude-code/write-tests"><img src="https://agentmods.dev/badge/commands/lukerenton/explore-claude-code/write-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.00000 | $0.00158 |
| Opus 5.5 | $0.00000 | $0.00063 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
write-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
Write tests for: $ARGUMENTS
Follow these conventions:
- Use Jest with TypeScript
- Use
describe/itblocks (nottest()) - Group by behaviour, not by method name
- Mock external services (database, APIs) - never hit real endpoints
- Include edge cases: empty input, null, boundary values, error paths
- Use descriptive test names:
it('returns 404 when user does not exist')
Structure:
describe('ComponentOrFunction', () => {
describe('when condition', () => {
it('should expected behaviour', () => {
// Arrange → Act → Assert
});
});
});
After writing the tests, run npm test to verify they pass.
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 · 22 lines · 0 tokens per session scan A 3940473b0101
write-tests is a command published in the GitHub repository LukeRenton/explore-claude-code (319 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 158 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
benchmark
Design and coordinate a reproducible Java performance test.
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
paydown
Pay down the frozen code-quality baseline and run a full QA sweep.
plan-feature
Production-grade feature planning with dual-AI validation (Claude + Antigravity/Gemini 3 via agy).
plan-refactor
Plan a refactor as a sequence of safe verified steps, with tests established before anything moves.
prompt-optimization
Improve an underperforming prompt through structured changes measured against fixed cases.