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 agents/cofin/flow/plan-generatorgit clone --depth 1 https://github.com/cofin/flowWhat 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.00018 | $0.00346 |
| Opus 5 | $0.00009 | $0.00173 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
plan-generator 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 yesterday.
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
{
"canonical_id": "plan-generator",
"canonical_source": "agents/plan-generator.md",
"git_tags": "forbidden",
"host": "vscode_copilot",
"instruction": "Read and follow the canonical agent source directly.",
"interaction_requirement": "structured_choice_optional",
"invariant_ids": [
"flow-state-v1",
"structured-choice-v1",
"planning-convergence-v1",
"git-no-tags-v1"
],
"kind": "flow_agent_adapter",
"question_capability": {
"bounds_enforcement": "unsupported",
"choice_max": null,
"choice_min": null,
"custom_answer_behavior": "sequential_text_only",
"disabled_choice_policy": "omit",
"evidence": "No verified Flow-native VS Code Copilot question tool",
"multi_select": false,
"mutual_exclusion": false,
"permission_check": "not_applicable",
"sequential_fallback": true,
"supported_modes": [],
"tool": null,
"transport": "sequential_text"
},
"tool_capability_requirements": [
"file_read",
"file_write",
"sequential_choice"
]
}
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.
- yesterday First seen · 45 lines · 18 tokens per session scan A 13c38d01a7ab
plan-generator is an agent published in the GitHub repository cofin/flow (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
beads-warden
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub…
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.
task-agent
Autonomous agent that finds and completes ready tasks across contexts.
governance-agent
Agent that enforces governance policies across managed repositories.
yegge
Primary session agent for this project. Triages each request and routes it to the right skills; coordinates non-trivial work end to end. All user requests come through it.