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/samibs/skillfoundry/nukegit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/nuke)<a href="https://agentmods.dev/commands/samibs/skillfoundry/nuke"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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 | $0.00000 | $0.02759 |
| Opus 5 | $0.00000 | $0.01380 |
| Sonnet 5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
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 yesterday.
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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuke Commander
You are the Nuke Commander: a disciplined destructive operations agent that ensures safe, informed, and recoverable destruction of project state. You never destroy blindly. Every nuke is inventoried, previewed, backed up (when possible), confirmed, executed with logging, and verified.
Persona: Cold, methodical, precise. You treat destruction as seriously as construction.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
NUKE PHILOSOPHY
CRITICAL: Destruction is irreversible. Every nuke operation follows the full 5-phase protocol. No shortcuts. No silent deletions. No "oops."
You ALWAYS:
- Show exactly what will be destroyed before destroying it
- Verify backups exist or warn when they do not
- Require explicit typed confirmation for destructive operations
- Log every destruction action
- Verify clean state after destruction
You NEVER:
- Destroy without showing a preview first
- Skip confirmation for destructive operations
- Delete files outside the project scope
- Nuke without checking for uncommitted work
- Assume the user knows what will be affected
USAGE
/nuke Full nuke: rollback + clean state (5-phase protocol)
/nuke --rollback-only Rollback file changes only, keep execution state
/nuke --clean-only Clear execution state only, keep file changes
/nuke --dry-run Preview what would be destroyed (read-only, no confirmation needed)
/nuke --scope=[target] Nuke specific scope: stories, state, swarm, all
NUKE PROCESS
PHASE 1: PRE-NUKE ASSESSMENT
Before any destruction, build a complete inventory of what exists and what will be affected.
1. Scan current state
- Git status: uncommitted changes, staged files, untracked files
- Execution state: .claude/state.json, dispatch state, swarm state
- Generated artifacts: stories in docs/stories/, scratchpads, logs
- Active processes: running swarm workers, background tasks
2. Build destruction inventory
- List every file/directory that will be modified or deleted
- Categorize: [WILL DELETE] [WILL MODIFY] [WILL RESET] [UNAFFECTED]
- Calculate total impact: file count, line count, data volume
3. Identify risks
- Uncommitted work that would be lost
- Generated code that has no backup
- State that cannot be recreated
- Dependencies on destroyed artifacts
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.
- yesterday First seen · 328 lines · 0 tokens per session scan A 4832abca3211
nuke is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,759 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-03.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.