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/davejj1530/planflow-greenlightWrote 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/davejj1530/planflow-greenlight/planflow)<a href="https://agentmods.dev/commands/davejj1530/planflow-greenlight/planflow"><img src="https://agentmods.dev/badge/commands/davejj1530/planflow-greenlight/planflow/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/davejj1530/planflow-greenlight/planflow"><img src="https://agentmods.dev/badge/commands/davejj1530/planflow-greenlight/planflow.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.00017 | $0.01020 |
| Opus 5.5 | $0.00007 | $0.00408 |
| Sonnet 5.5 | $0.00003 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
planflow 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the PlanFlow workflow. The task is:
$ARGUMENTS
Follow this workflow exactly. Do not skip the approval step and do not use native plan mode or the ExitPlanMode tool.
1. Investigate
Read whatever code, configs, or docs you need to plan this task well. Do not modify any file and do not run any state-changing command yet.
2. Draft the plan
Break the task into 3 to 9 concrete steps. Each step needs:
title: a short imperative phrase (under 60 characters), e.g. "Add rate-limit middleware".detail: 1 to 3 sentences saying exactly what will change, in which files, and why.id: a stable id (s1,s2, ...) so other steps can reference it.
Three optional fields express structure. Use them only when the plan genuinely has it; a simple sequence needs none of them:
after: array of step ids that must complete first. Use for real branches, joins, or order-independent steps. A step withoutafterfollows the previous step.condition: short label for when a step runs, e.g."cache hit"or"tests fail". It renders on the step's incoming edge. Treat it as binding during execution: only run the step when its condition holds.feature: workstream name when one plan spans distinct features. Steps sharing afeatureare enclosed together on the canvas.
Worked example, a conditional fork inside one feature:
{ "id": "s2", "title": "Add cache lookup", "feature": "Caching", "after": ["s1"] }
{ "id": "s3", "title": "Serve cached response", "feature": "Caching", "after": ["s2"], "condition": "cache hit" }
{ "id": "s4", "title": "Fetch upstream and store", "feature": "Caching", "after": ["s2"], "condition": "cache miss" }
Steps must be ordered so that each one can be executed after its dependencies. Also write a one-paragraph summary of the overall approach and any tradeoffs.
3. Request approval in the browser
Call the request_plan_approval tool from the planflow MCP server with:
title: a short name for the plan (e.g. "Rate limiting for the API")summary: the paragraph from step 2steps: the array of steps
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 · 63 lines · 17 tokens per session scan A 16f9c455c7f0
planflow is a command published in the GitHub repository davejj1530/planflow-greenlight (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,020 once invoked, about $0.0001 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-31.