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/agentsea/flashbackerWrote 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/agentsea/flashbacker/update-tasks)<a href="https://agentmods.dev/commands/agentsea/flashbacker/update-tasks"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/update-tasks/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/agentsea/flashbacker/update-tasks"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/update-tasks.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.02074 |
| Opus 5.5 | $0.00000 | $0.00830 |
| Sonnet 5.5 | $0.00000 | $0.00415 |
| Haiku 4.5 | $0.00000 | $0.00207 |
Grade A, and why
update-tasks 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Task Progress and Completion
Mark tasks as complete, update progress tracking, and maintain task dashboards.
Directory Structure
docs/tasks/ # Task files location (read/write here)
├── ISSUE-XXX-name/ # Per-issue task directories
│ ├── README.md # Task progress dashboard (update this)
│ ├── phase-1-name.md # Phase task files (update checkboxes here)
│ ├── phase-2-name.md # Additional phase files
│ └── phase-N-name.md # All phase files for completion tracking
docs/issues/ # Issue files location (reference only)
├── ISSUE-XXX-title.md # Parent issue files
└── README.md # Issue tracking (may update status here)
Usage
/fb:update-tasks <issue-number> <action> [task-id] [notes]
Examples:
/fb:update-tasks ISSUE-027 complete 1.1.1- Mark task 1.1.1 as complete/fb:update-tasks ISSUE-027 start 2.1.1- Mark task as started/in-progress/fb:update-tasks ISSUE-027 block 1.3.2 waiting for security review- Block task with reason/fb:update-tasks ISSUE-027 dashboard- Regenerate progress dashboard/fb:update-tasks ISSUE-027 complete 1.1.2 implemented template signer- Complete with notes
Command Implementation
Parse the command arguments:
- Argument 1 (required): Issue number (ISSUE-027, ISSUE-015, etc.)
- Argument 2 (required): Action (complete, start, block, dashboard, progress)
- Argument 3 (conditional): Task ID for complete/start/block actions (1.1.1, 2.3.4, etc.)
- Argument 4+ (optional): Notes or reason text (remaining arguments joined as text)
Argument Parsing Logic
- Extract Issue Number: First argument must match ISSUE-XXX pattern
- Extract Action: Second argument determines operation type
- Extract Task ID: Third argument for actions requiring specific task
- Extract Notes/Reason: Remaining arguments joined as notes or block reason
- Validate Inputs: Ensure issue exists and task ID is valid format
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 · 206 lines · 0 tokens per session scan A c88048d2ef3a
update-tasks is a command published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,074 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
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.