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/nuke.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/nuke)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/nuke"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/nuke.svg" alt="Measured on agentmods" 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.04398 |
| Opus 5 | $0.00000 | $0.02199 |
| Sonnet 5 | $0.00000 | $0.00880 |
| Haiku 4.5 | $0.00000 | $0.00440 |
Grade A, and why
nuke 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.
How it starts
The opening of the file, as written. The whole thing — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nuke
allowed-tools: Task(), Read(), Write(), Edit(), MultiEdit(), Glob(), Grep(), Bash(), LS(), mcp__zen__, mcp__genie-memory__, mcp__send_whatsapp_message__ description: Enhanced 3-Layer Parallel Nuclear Debugging with Checkpoint Recovery
🚨 NUCLEAR DEBUGGING 🚨
When traditional debugging fails, /nuke systematically tests ALL zen combinations to find the solution.
When to Use /nuke
- ✅ After standard debugging fails: Tried
/debug, manual investigation - ✅ Complex/mysterious bugs: Race conditions, memory leaks, integration issues
- ✅ Critical production issues: Need solution ASAP, willing to use all resources
- ✅ Multi-system problems: Bug spans multiple components/services
- ❌ Simple issues: Use regular
/debugfirst - ❌ Known patterns: Search memory first
Usage
# Basic nuclear debugging
/nuke "Ana team routes to wrong agent on Portuguese queries about cartão"
# With specific focus
/nuke "Memory leak in agent sessions after 1000+ requests" focus="performance,memory"
# With time limit (default: 30 minutes)
/nuke "Race condition in payment processing" time_limit="45m"
Enhanced 3-Layer Parallel Nuclear Architecture
🔍 Layer 1: Parallel Investigation
Smart model selection for optimal analysis
Model Selection Strategy:
investigation_models:
complex_systems: "gemini-2.5-pro" # 1M context, thinking mode
logical_debugging: "o3" # Strong reasoning chains
performance_analysis: "grok" # Large context analysis
quick_patterns: "o4-mini" # Fast pattern recognition
architectural_review: "gemini-2.5-pro" # Deep architectural insight
Parallel Investigation Execution:
- Task 1:
mcp__zen__debug- Traditional debugging workflow - Task 2:
mcp__zen__analyze- Architectural analysis - Task 3:
mcp__zen__thinkdeep- Deep investigation - Task 4:
mcp__zen__tracer- Code flow tracing (if code-related)
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 · 527 lines · 0 tokens per session scan A 82c06266bd4e
nuke 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 4,398 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.