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/jnarowski/agentcmd/remove-specgit clone --depth 1 https://github.com/jnarowski/agentcmdWhat 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.00010 | $0.00480 |
| Opus 5 | $0.00005 | $0.00240 |
| Sonnet 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 today.
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.
- today 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 8mo ago), licensed MIT. It adds 10 tokens to every session and 480 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.