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.
git clone --depth 1 https://github.com/ankushdixit/claude-pluginsWrote 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/ankushdixit/claude-plugins/work-delete)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/work-delete"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/work-delete/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/ankushdixit/claude-plugins/work-delete"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/work-delete.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.00007 | $0.00263 |
| Opus 5.5 | $0.00003 | $0.00105 |
| Sonnet 5.5 | $0.00001 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
work-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 1mo 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.
What it actually says
Work Item Delete
Delete a work item from the system with optional spec file removal.
Usage
sk work-delete "$@"
The work item ID is provided in $ARGUMENTS and passed through "$@".
What It Does
The command will:
- Display work item details and check for dependents
- Warn if other work items depend on this one
- Prompt for confirmation with options:
- Delete work item only (keep spec file)
- Delete both work item and spec file
- Cancel deletion
- Execute deletion based on your selection
- Remind you to update dependent work items if needed
Examples
sk work-delete feature_obsolete_item
sk work-delete bug_fixed_issue
Important Notes
- Deletion is permanent - Work items cannot be recovered
- Dependents are NOT modified - If other items depend on the deleted item, you must manually update them using
/work-update <id> remove-dependency - Spec files are optional - You can choose to keep the spec file for reference
Show all command output to the user in a clear, formatted display.
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.
- 1mo ago First seen · 45 lines · 7 tokens per session scan A fe715cdc6dfd
work-delete is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 263 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.