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/tasks-status)<a href="https://agentmods.dev/commands/agentsea/flashbacker/tasks-status"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/tasks-status/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/tasks-status"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/tasks-status.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.02302 |
| Opus 5.5 | $0.00000 | $0.00921 |
| Sonnet 5.5 | $0.00000 | $0.00460 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
tasks-status 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Status Dashboard
Display comprehensive progress dashboard across all active issues with granular task tracking.
Directory Structure
docs/tasks/ # Task files location (read from here)
├── ISSUE-XXX-name/ # Per-issue task directories
│ ├── README.md # Task progress dashboards (read these)
│ ├── phase-1-name.md # Phase task files (scan for completion)
│ ├── phase-2-name.md # Additional phase files
│ └── phase-N-name.md # All phase files for status analysis
docs/issues/ # Issue files location (reference for context)
├── ISSUE-XXX-title.md # Issue titles and descriptions
└── README.md # Issue priority and status reference
Usage
/fb:tasks-status [issue-number] [view-type]
Examples:
/fb:tasks-status- Show overview of all active issues with tasks/fb:tasks-status ISSUE-027- Detailed view of specific issue's task progress/fb:tasks-status blocked- Show only blocked tasks across all issues/fb:tasks-status ISSUE-027 detailed- Full task breakdown with acceptance criteria/fb:tasks-status summary- High-level summary for quick status check
Command Implementation
Parse the command arguments:
- Argument 1 (optional): Issue number (ISSUE-027, ISSUE-015) or view type (blocked, summary, detailed)
- Argument 2 (optional): View type if first argument was issue number
Argument Parsing Logic
- Check First Argument: If matches ISSUE-XXX pattern, it's an issue number
- Determine View Type: Look for "detailed", "blocked", "summary" in arguments
- Set Scope: Issue-specific view or all-issues view based on presence of issue number
- Default Behavior: If no arguments, show overview of all active issues
Dashboard Views
Default Overview (All Issues)
# SoftMachine Task Progress Overview
## Active Issues with Tasks
┌─────────────┬──────────────────────────────────┬──────────┬──────────┐
│ Issue │ Title │ Progress │ Status │
├─────────────┼──────────────────────────────────┼──────────┼──────────┤
│ ISSUE-027 │ Railway-Native Scaffolding │ 15/52 │ 🔄 Phase 2│
│ ISSUE-015 │ Security Vulnerabilities │ 3/4 │ 🔄 Phase 1│
│ ISSUE-019 │ SMPA Architectural Compliance │ 0/8 │ ⏳ Waiting│
└─────────────┴──────────────────────────────────┴──────────┴──────────┘
## Current Focus
**Primary**: ISSUE-027.2.1.2 Railway GraphQL client authentication
**Secondary**: ISSUE-015.1.3 Input validation security patterns
## Recent Completions (Last 7 Days)
- ✅ ISSUE-027.1.1.4 Template integrity validation (2025-08-14)
- ✅ ISSUE-027.1.2.3 Package verification system (2025-08-14)
- ✅ ISSUE-015.1.1 Shell injection fix validation (2025-08-13)
## Blocked Tasks (Requiring Attention)
- 🚫 ISSUE-027.3.1.1 Template repository design (waiting for Phase 2 completion)
- 🚫 ISSUE-019.1.1 SMPA compliance audit (waiting for ISSUE-015 completion)
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 · 248 lines · 0 tokens per session scan A c6d99aaad69a
tasks-status 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,302 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.