delete

A command for removing a specified piece of code, such as a symbol, file, feature, endpoint, job, or command, along with related cleanup. It requires a separate code-deletion-cleanup skill to guide the work.

In plain words
What is it for?
Use it when retiring code and checking the working tree, recent commits, and a tracked queue of remaining cleanup tasks.
Why use it?
It helps prevent incomplete deletion, such as leaving unused references or related files behind. The deletion target must be exact when the command is started.

Command

Install

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.

agentmods
npx agentmods add commands/crypticswarm/swarmforge/delete
Clone the repo
git clone --depth 1 https://github.com/CrypticSwarm/Swarmforge
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.00143
Opus 5 $0.00003 $0.00072
Sonnet 5 $0.00001 $0.00029
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash 58e0f7f66a17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

delete 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.

commands/delete.md · 22 lines

What it actually says

Activate the code-deletion-cleanup skill before taking any other action.

Deletion target: $ARGUMENTS

If no deletion target is provided, ask for the exact symbol, file path, feature, endpoint, job, or command to remove and stop.

Current working tree: !git status --short

Recent commits: !git log --oneline -10

Follow the code-deletion-cleanup skill exactly. Use todowrite as the canonical deletion queue. It is acceptable to have multiple in_progress todos while subagents run in parallel. At the end of each iteration, report what remains in the queue.

Changes

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.

  1. yesterday First seen · 22 lines · 5 tokens per session scan A 58e0f7f66a17

Subscribe to this mod's changes

delete is a command published in the GitHub repository CrypticSwarm/Swarmforge (2 stars, last pushed 2d ago), licensed MIT. It adds 5 tokens to every session and 143 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.