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/agentsea/flashbackernpx agentmods add commands/agentsea/flashbacker/create-tasksWrote 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/create-tasks)<a href="https://agentmods.dev/commands/agentsea/flashbacker/create-tasks"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/create-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/create-tasks"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/create-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.01614 |
| Opus 5.5 | $0.00000 | $0.00646 |
| Sonnet 5.5 | $0.00000 | $0.00323 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
create-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Granular Tasks from Issue
Generate atomic, AI-friendly task breakdown from comprehensive issues following the ai-dev-tasks methodology.
Directory Structure
docs/issues/ # Source issue files (read from here)
├── ISSUE-XXX-title.md # Individual issue files to analyze
└── README.md # Issue tracking reference
docs/tasks/ # Task files location (write to here)
├── ISSUE-XXX-name/ # Per-issue task directories (create these)
│ ├── README.md # Task progress dashboard
│ ├── phase-1-name.md # Granular tasks for Phase 1
│ ├── phase-2-name.md # Granular tasks for Phase 2
│ └── phase-N-name.md # Additional phases as needed
└── metadata.json # Task metadata and tracking
Usage
/fb:create-tasks <issue-number> [force] [phases]
Examples:
/fb:create-tasks ISSUE-027- Generate full task breakdown for XYZ project scaffolding/fb:create-tasks ISSUE-015 force- Regenerate tasks, overwrite existing/fb:create-tasks ISSUE-027 phases:1,2- Generate only specific phases
Command Implementation
Parse the command arguments:
- Argument 1 (required): Issue number (ISSUE-027, ISSUE-015, etc.)
- Argument 2 (optional): "force" to overwrite existing task files
- Argument 3 (optional): "phases:1,2,3" to generate only specific phases
Argument Parsing Logic
- Extract Issue Number: First argument must match ISSUE-XXX pattern
- Check Force Flag: Look for "force" in arguments to enable overwrite
- Parse Phases: Look for "phases:" prefix followed by comma-separated numbers
- Validate Issue: Ensure issue file exists in docs/issues/ directory
How It Works
Step 1: Issue Analysis
- Read Issue File: Load
docs/issues/ISSUE-XXX-*.md - Parse Structure: Extract phases, deliverables, acceptance criteria
- Identify Dependencies: Map dependencies between phases and tasks
- Validate Scope: Ensure issue is suitable for task breakdown
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 · 174 lines · 0 tokens per session scan A f7b83383c100
create-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 1,614 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.