Borrowing it
Nothing to install: this file belongs to gpt-cmdr/ras-commander. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gpt-cmdr/ras-commander/main/.claude/commands/agent-taskupdate.mdgit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWrote 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/gpt-cmdr/ras-commander/agent-taskupdate)<a href="https://agentmods.dev/commands/gpt-cmdr/ras-commander/agent-taskupdate"><img src="https://agentmods.dev/badge/commands/gpt-cmdr/ras-commander/agent-taskupdate/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/gpt-cmdr/ras-commander/agent-taskupdate"><img src="https://agentmods.dev/badge/commands/gpt-cmdr/ras-commander/agent-taskupdate.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.00000 | $0.00800 |
| Opus 5.5 | $0.00000 | $0.00320 |
| Sonnet 5.5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
agent-taskupdate 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Look at your task list and memory, assess your current progress, and make a detailed plan to continue making progress on your task list.
Task Update Protocol
1. Read Current State (Do This First)
Read the following files to understand the current situation:
agent_tasks/.agent/STATE.md -- Current project state, what's in progress
agent_tasks/.agent/PROGRESS.md -- Recent session history (last 2-3 entries)
agent_tasks/.agent/BACKLOG.md -- All tasks and their status
If these files don't exist, look for task planning documents in agent_tasks/ root or agent_tasks/tasks/.
2. Assess Current Progress
For the currently in-progress task:
- What was accomplished in the last session?
- Are there blockers?
- What is the next concrete action?
For the backlog:
- Are any "Blocked" tasks now unblocked?
- Have new tasks emerged from the current work?
3. Update STATE.md
Update agent_tasks/.agent/STATE.md with:
- Current timestamp
- What is currently in progress
- Health status (Green / Yellow / Red)
- Any blockers discovered
- Next priorities
STATE.md format:
# Project State
**Last Updated**: {YYYY-MM-DD HH:MM}
**Session**: {N}
**Health**: Green | Yellow | Red
## Current Focus
{What task is actively being worked on}
## Next Priorities
1. {Priority 1}
2. {Priority 2}
## Blockers
- {Any blockers, or "None"}
## Recent Accomplishments
- {What was done recently}
4. Append to PROGRESS.md
Append a new session entry to agent_tasks/.agent/PROGRESS.md:
## Session {N} — {YYYY-MM-DD}
### Accomplished
- {What was done}
### Decisions Made
- {Any key decisions and rationale}
### Files Modified
- {List of files}
### Handoff Notes
{Context the next session needs to know immediately}
### Next Session Should Start With
1. {First action}
2. {Second action}
PROGRESS.md is append-only — never edit previous entries.
5. Update BACKLOG.md
Update task status:
- Mark completed tasks with
[x] - Add any new tasks discovered
- Move newly-unblocked tasks from Blocked to Ready
- Add notes to tasks based on current findings
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 · 130 lines · 0 tokens per session scan A e36742aedd1a
agent-taskupdate is a command published in the GitHub repository gpt-cmdr/ras-commander (88 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 800 tokens. 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-30.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.