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.
npx agentmods add commands/agentsea/flashbacker/work-taskgit clone --depth 1 https://github.com/agentsea/flashbackerWhat 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 | $0.00000 | $0.01574 |
| Opus 5 | $0.00000 | $0.00787 |
| Sonnet 5 | $0.00000 | $0.00315 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
work-task 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 2d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work on Specific Atomic Task
Focus AI attention on a single atomic task with full context and clear deliverables.
Directory Structure
docs/tasks/ # Task files location (read from here)
├── ISSUE-XXX-name/ # Per-issue task directories
│ ├── README.md # Task progress dashboard
│ ├── phase-1-name.md # Task file containing specific tasks
│ ├── phase-2-name.md # Additional phase files
│ └── phase-N-name.md # Phase files to search for task
docs/issues/ # Issue files location (reference for context)
├── ISSUE-XXX-title.md # Parent issue for background context
└── README.md # Issue tracking for dependencies
Usage
/fb:work-task <task-id> [context] [verify] [dependency-check]
Examples:
/fb:work-task ISSUE-027.1.1.1- Work on template signing research task/fb:work-task ISSUE-027.2.3.2 context- Include full project context for complex task/fb:work-task ISSUE-015.1.2 verify- Complete task and verify acceptance criteria/fb:work-task ISSUE-027.1.1.4 dependency-check- Check dependencies before starting
Command Implementation
Parse the command arguments:
- Argument 1 (required): Task ID in format ISSUE-XXX.PHASE.CATEGORY.TASK
- Argument 2 (optional): "context" to include full project memory and working plan
- Argument 3 (optional): "verify" to check acceptance criteria after completion
- Argument 4 (optional): "dependency-check" to validate prerequisites
Argument Parsing Logic
- Extract Task ID: First argument must match ISSUE-XXX.N.N.N pattern
- Parse Components: Split task ID into issue, phase, category, task numbers
- Check Flags: Look for "context", "verify", "dependency-check" in remaining arguments
- Validate Task: Ensure task exists in appropriate phase file
How It Works
Step 1: Task Loading
- Parse Task ID: Extract issue number, phase, category, and task number
- Load Task File: Read
docs/tasks/ISSUE-XXX/phase-N-name.md - Extract Task Details: Get specific task, deliverables, acceptance criteria
- Check Dependencies: Validate prerequisite tasks are marked complete
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.
- 2d ago First seen · 166 lines · 0 tokens per session scan A 5bec6acd8ff7
work-task is a command published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,574 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.