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/refactorgit 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.00009 | $0.00154 |
| Opus 5 | $0.00005 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
refactor 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
Refactoring Task
Please refactor the provided code focusing on:
1. Code Structure
- Extract reusable functions/components
- Reduce complexity and nesting
- Improve modularity
- Apply design patterns where appropriate
2. Naming & Clarity
- Use descriptive variable and function names
- Remove magic numbers and strings
- Add meaningful comments
- Improve code readability
3. Performance
- Optimize algorithms
- Reduce redundant operations
- Improve resource usage
- Consider caching where appropriate
4. Maintainability
- Reduce dependencies
- Improve testability
- Follow language conventions
- Update documentation
Provide before/after comparisons and explain the improvements.
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 · 34 lines · 9 tokens per session scan A 2344414c523b
refactor is a command published in the GitHub repository LEEI1337/phantom-neural-cortex (5 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 154 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
OPSX: Bulk Archive
Archive multiple completed changes at once.
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.
transcribe
Transcribe and summarize an AUDIO or VIDEO file (or a YouTube/remote URL) with Antigravity (agy / Gemini 3.x multimodal) — something Claude can't do natively. Voice notes, meetings, calls, screencasts. Faithful transcript + summary; timestamps for video/URLs. Saves to docs/agy/transcripts/.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
maestro-next
Unified entry for all development intents — classify intent, assess complexity, route to the correct execution channel: /maestro-companion (lightweight), standard single run, or /maestro and /maestro-ralph (multi-step manual/orchestrated). Pure router, never runs execution loops itself.