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/lukerenton/explore-claude-code/write-testsgit clone --depth 1 https://github.com/LukeRenton/explore-claude-codeWhat 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.00000 | $0.00158 |
| Opus 5 | $0.00000 | $0.00079 |
| Sonnet 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 2d 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.
- 2d 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 (309 stars, last pushed 21d 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
tests
Run the Week 4 backend test workflow. Build TESTARGS from $ARGUMENTS: use backend/tests when it is empty; prepend backend/tests when it starts with an option such as -k; otherwise use the supplied path or node ID as-is.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
go-test
Go TDD workflow with table-driven tests.
test
Command "test" from shenjingnan/xiaozhi-client, covering test command, 执行步骤, 测试配置, 测试文件位置 and 常用命令.
write-fixtures
../../skills/write-fixtures/SKILL.md.