Borrowing it
Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/remove-spec.mdgit clone --depth 1 https://github.com/jnarowski/agentcmdWrote 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/jnarowski/agentcmd/remove-spec)<a href="https://agentmods.dev/commands/jnarowski/agentcmd/remove-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/remove-spec/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/remove-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/remove-spec.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00480 |
| Opus 5.5 | $0.00004 | $0.00192 |
| Sonnet 5.5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade C, and why
remove-spec scanned grade C with 1 finding 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 2mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Remove the spec folder using `rm -rf` What it actually says
Remove Spec
Permanently delete a spec folder and remove its entry from the specs index. This command does not ask for confirmation.
Variables
- $spec-identifier: $1 (required) - The spec ID (e.g., "251112054939-workflow-resync"), name (e.g., "workflow-resync"), or relative/absolute path to the spec folder
Instructions
- This command permanently deletes the spec folder - there is no confirmation step
- Remove the spec entry from
.agent/specs/index.json - If the spec is not found, report an error and list available specs
- Handle both full spec IDs and partial name matches
Workflow
-
Parse the spec identifier and locate the spec folder:
- If $spec-identifier is an absolute path, use it directly
- If it starts with
.agent/specs/, treat as relative path - Otherwise, search
.agent/specs/index.jsonfor matching ID or name - Check all workflow folders:
backlog/,todo/,in-progress/,done/
-
Delete the spec folder and update index:
- Remove the spec folder using
rm -rf - Load
.agent/specs/index.json - Remove the matching spec entry from the JSON
- Write updated index back to file
- Remove the spec folder using
-
Report the deletion:
- Show the spec name and folder that was deleted
- Confirm removal from index.json
Error Handling
- If spec not found: List all available specs with their IDs and locations
- If index.json malformed: Report error and suggest manual inspection
- If deletion fails: Report filesystem error
Examples
# Remove by full ID
/remove-spec 251112054939-workflow-resync
# Remove by name match
/remove-spec workflow-resync
# Remove by path
/remove-spec .agent/specs/todo/251112054939-workflow-resync
Report
Return:
- Spec name and ID that was deleted
- Full path to the deleted folder
- Confirmation that index.json was updated
- If error: Clear error message and list of available specs
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.
- 2mo ago First seen · 65 lines · 10 tokens per session scan C efecf59d5793
remove-spec is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 480 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
remove-spec compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| remove-specjnarowski/agentcmd | Command | 18 | 10mo ago | MIT | C | 10 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |