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/cofin/flowWrote 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/cofin/flow/flow-task)<a href="https://agentmods.dev/commands/cofin/flow/flow-task"><img src="https://agentmods.dev/badge/commands/cofin/flow/flow-task/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/cofin/flow/flow-task"><img src="https://agentmods.dev/badge/commands/cofin/flow/flow-task.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.00008 | $0.00471 |
| Opus 5.5 | $0.00003 | $0.00188 |
| Sonnet 5.5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
flow-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 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.
What it actually says
{
"agent": "executor",
"argument_schema": {
"optional": [],
"required": [
"exploration"
],
"syntax": "<exploration>"
},
"bounds_enforcement": "agent_validated",
"canonical_id": "flow/task",
"capability_evidence": "Claude Code declared AskUserQuestion contract",
"choice_max": 4,
"choice_min": 2,
"completion_gates": [
"worksheet_complete",
"evidence_captured"
],
"custom_answer_behavior": "native_custom_input",
"disabled_choice_policy": "omit",
"fallback": "Use Flow to create an exploration task",
"git_tags": "forbidden",
"host": "claude_code",
"instruction": "Load the lifecycle owner and follow the canonical procedure source directly.",
"interaction_mode": "none",
"invocation": "/flow-task",
"kind": "flow_command_adapter",
"lifecycle_owner": "flow-planning",
"multi_select": true,
"mutability": "planning_write",
"mutual_exclusion": true,
"plan_capability": "preferred",
"procedure_source": "skills/flow/references/task.md",
"question_capability": null,
"question_permission_check": "declared_and_allowed",
"question_tool": "AskUserQuestion",
"question_transport": "conditional_native",
"runtime_dependency": "agent_file_tools_only",
"sequential_fallback": true,
"shared_contracts": [
"flow-state-v1",
"worksheet-execution-v1"
],
"state_operations": [
"create",
"claim",
"discover",
"release",
"close"
],
"supported_selection_modes": [
"binary",
"single_select",
"multi_select"
]
}
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 · 65 lines · 8 tokens per session scan A 789d149bd23b
flow-task is a command published in the GitHub repository cofin/flow (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 471 once invoked, about $0.0000 per session on Opus 5.5. 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
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
lavra-retro
Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
lavra-recall
Search knowledge base mid-session and inject relevant context.
test-browser
Run browser tests on pages affected by current PR or branch.
lavra-quick
Fast-track small tasks — abbreviated plan then straight to execution.