Borrowing it
Nothing to install: this file belongs to LEEI1337/phantom-neural-cortex. 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/LEEI1337/phantom-neural-cortex/master/.claude/commands/test.mdgit clone --depth 1 https://github.com/LEEI1337/phantom-neural-cortexWrote 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/leei1337/phantom-neural-cortex/test)<a href="https://agentmods.dev/commands/leei1337/phantom-neural-cortex/test"><img src="https://agentmods.dev/badge/commands/leei1337/phantom-neural-cortex/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/leei1337/phantom-neural-cortex/test"><img src="https://agentmods.dev/badge/commands/leei1337/phantom-neural-cortex/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.00006 | $0.00155 |
| Opus 5.5 | $0.00002 | $0.00062 |
| Sonnet 5.5 | $0.00001 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 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
Test Generation Task
Please generate comprehensive tests for the provided code including:
1. Unit Tests
- Test individual functions/methods
- Cover edge cases and boundary conditions
- Test error handling
- Mock external dependencies
2. Integration Tests
- Test component interactions
- Verify data flow between modules
- Test API endpoints (if applicable)
3. Test Coverage
- Aim for high code coverage
- Focus on critical paths
- Include negative test cases
4. Test Structure
- Use appropriate testing framework
- Follow AAA pattern (Arrange, Act, Assert)
- Clear test descriptions
- Proper setup and teardown
Please include both test code and explanations.
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 · 32 lines · 6 tokens per session scan A 87d5c17c5ae3
test is a command published in the GitHub repository LEEI1337/phantom-neural-cortex (5 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 155 once invoked, about $0.0000 per session on Opus 5.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
handoff
Hand a whole, test-covered task to Antigravity (agy/Gemini) and verify it only by running the tests — the one delegation shape measured cheaper than Claude Code alone.
review.speckit-test
Review the test automation implementation against the specification and the desired test pyramid shape; detect and explain misalignment - prioritise unit tests, identify high-value gaps and brittle tests, and provide actionable recommendations (including refactoring) to improve behavioural confidence.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
write-unit-tests
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.