Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fergupa/claude_pluginsnpx agentmods add commands/fergupa/claude_plugins/updateWrote 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/fergupa/claude_plugins/update)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/update"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/update.svg" alt="Measured on agentmods" 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.00009 | $0.01160 |
| Opus 5 | $0.00005 | $0.00580 |
| Sonnet 5 | $0.00002 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
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 3d 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.
This is a copy
100% identical to update — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Command
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Keep your task list and memory current. Two modes:
- Default: Sync tasks from external tools, triage stale items, check memory for gaps
--comprehensive: Deep scan chat, email, calendar, docs — flag missed todos and suggest new memories
Usage
/productivity:update
/productivity:update --comprehensive
Default Mode
1. Load Current State
Read TASKS.md and memory/ directory. If they don't exist, suggest /productivity:start first.
2. Sync Tasks from External Sources
Check for available task sources:
- Project tracker (e.g. Asana, Linear, Jira) (if MCP available)
- GitHub Issues (if in a repo):
gh issue list --assignee=@me
If no sources are available, skip to Step 3.
Fetch tasks assigned to the user (open/in-progress). Compare against TASKS.md:
| External task | TASKS.md match? | Action |
|---|---|---|
| Found, not in TASKS.md | No match | Offer to add |
| Found, already in TASKS.md | Match by title (fuzzy) | Skip |
| In TASKS.md, not in external | No match | Flag as potentially stale |
| Completed externally | In Active section | Offer to mark done |
Present diff and let user decide what to add/complete.
3. Triage Stale Items
Review Active tasks in TASKS.md and flag:
- Tasks with due dates in the past
- Tasks in Active for 30+ days
- Tasks with no context (no person, no project)
Present each for triage: Mark done? Reschedule? Move to Someday?
4. Decode Tasks for Memory Gaps
For each task, attempt to decode all entities (people, projects, acronyms, tools, links):
Task: "Send PSR to Todd re: Phoenix blockers"
Decode:
- PSR → ✓ Pipeline Status Report (in glossary)
- Todd → ✓ Todd Martinez (in people/)
- Phoenix → ? Not in memory
Track what's fully decoded vs. what has gaps.
5. Fill Gaps
Present unknown terms grouped:
I found terms in your tasks I don't have context for:
1. "Phoenix" (from: "Send PSR to Todd re: Phoenix blockers")
→ What's Phoenix?
2. "Maya" (from: "sync with Maya on API design")
→ Who is Maya?
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.
- 3d ago First seen · 168 lines · 9 tokens per session scan A 7d0c2cd50b6c
update is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,160 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to update, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.