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/leei1337/phantom-neural-cortex/testgit clone --depth 1 https://github.com/LEEI1337/phantom-neural-cortexWhat 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.00006 | $0.00155 |
| Opus 5 | $0.00003 | $0.00077 |
| Sonnet 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 3d 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.
- 3d 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 6mo ago), licensed MIT. It adds 6 tokens to every session and 155 once invoked, about $0.0000 per session on Opus 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
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
testing
Testing hub - run tests, coverage analysis, TDD, benchmarks.
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.
go-test
Go TDD workflow with table-driven tests.
result
Fetch the output of a finished background Antigravity (agy) job, then verify it.
consensus
Fan out, then run one arbiter pass that synthesizes a single verdict.