Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-cli/main/.claude/commands/test.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/test)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/test"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/test/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/namastexlabs/automagik-cli/test"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/test.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.00977 |
| Opus 5 | $0.00000 | $0.00489 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
test 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test
allowed-tools: Task(), Read(), Write(), Edit(), MultiEdit(), Bash(), Glob(), Grep(), mcp__gemini__, mcp__search-repo-docs__, mcp__genie_memory__, mcp__send_whatsapp_message__ description: Generate comprehensive test suites
Generate comprehensive test suites with edge case coverage and expert guidance.
Auto-Loaded Project Context:
@/CLAUDE.md @/docs/ai-context/project-structure.md @/docs/ai-context/docs-overview.md
Usage
# Default (uses Claude)
/test "Generate tests for User.login() method"
# With specific model
/test "Test payment processing validation" model="o3"
/test "Create tests for auth error handling" model="grok"
/test "Generate integration tests for API" model="gemini"
Intelligent Test Strategy
Step 1: Test Analysis
Parse user request: "$ARGUMENTS"
Test Categories:
- Unit Tests → Individual function/method testing
- Integration Tests → Component interaction testing
- Edge Case Tests → Boundary and error condition testing
- Performance Tests → Load and stress testing
Thinking Modes
- low: Simple functions (8% depth)
- medium: Standard modules (33% depth) - DEFAULT
- high: Complex systems with many interactions (67% depth)
- max: Critical systems requiring exhaustive coverage (100% depth)
Test Types
Generates:
- Unit tests with mocking
- Integration tests
- Edge case scenarios
- Error handling tests
- Performance tests (when applicable)
- Security tests (when applicable)
Examples
# Specific function tests
/test "Test UserService.authenticate() with all edge cases"
# Module testing
/test "Generate tests for entire payment module" model="o3"
# Complex integration
/test "Test agent routing with 20+ scenarios" thinking_mode="high"
# Critical system
/test "Exhaustive tests for encryption module" model="gemini" thinking_mode="max"
Best Practices
- Be Specific: Target specific functions/classes rather than "test everything"
- Provide Context: Include what the code does if not obvious
- Follow Patterns: Tests will match your existing test framework
- Review Coverage: Generated tests aim for high coverage
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.
- 4d ago First seen · 144 lines · 0 tokens per session scan A 910969fa3f73
test is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 977 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-09-04.
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.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.
implement-fix
Minimal pipeline for test-fixing tasks.