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/ankushdixit/claude-plugins/work-updategit clone --depth 1 https://github.com/ankushdixit/claude-pluginsWhat 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.00004 | $0.00489 |
| Opus 5 | $0.00002 | $0.00244 |
| Sonnet 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 2d 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.
- 2d 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 7mo ago), licensed MIT. It adds 4 tokens to every session and 489 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.
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.