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-update)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/work-update"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/work-update/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-update"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/work-update.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.00004 | $0.00489 |
| Opus 5.5 | $0.00002 | $0.00196 |
| Sonnet 5.5 | $0.00001 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
work-update 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 Update
Update specific fields of an existing work item.
Usage
sk work-update "$@"
The work item ID and field are provided in $ARGUMENTS and passed through "$@".
Supported Fields
- status - Update status (not_started/in_progress/blocked/completed)
- priority - Change priority level (critical/high/medium/low)
- milestone - Set or update milestone
- add-dependency - Add dependency relationships
- remove-dependency - Remove existing dependencies
- set-urgent - Mark work item as urgent (only one item can be urgent at a time)
- clear-urgent - Remove urgent flag from work item
What It Does
The command will:
- Display current work item details
- Prompt for the new value based on field type
- Show available options for selection (priority, dependencies, etc.)
- Validate changes and update the work item
- Display confirmation with old → new values
Examples
sk work-update feat_001 --status in_progress
sk work-update feat_001 --priority critical
sk work-update feat_001 --add-dependency bug_002
sk work-update feat_001 --milestone "v1.0"
sk work-update feat_001 --status completed --priority high
sk work-update feat_001 --set-urgent
sk work-update feat_001 --clear-urgent
Field-Specific Behavior
Status: Update to not_started, in_progress, blocked, or completed
Priority: Change to critical, high, medium, or low
Milestone: Set milestone name (e.g., "Sprint 1", "v1.0", "Q1 2025")
Add-dependency: Add work item IDs as dependencies (comma-separated)
Remove-dependency: Remove work item IDs from dependencies (comma-separated)
Set-urgent: Mark this item as urgent (requires immediate attention). Only ONE item can be urgent at a time. If another item is already urgent, it will be automatically cleared.
Clear-urgent: Remove the urgent flag from this work item
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 · 67 lines · 4 tokens per session scan A 20f39e01a61c
work-update is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 4 tokens to every session and 489 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.