plan

A command that turns an idea or document into a local, recoverable workflow blueprint. A workflow blueprint describes the planned work and its related objects before anything is uploaded.

In plain words
What is it for?
Use it to plan workflow projects, check for duplicates and dependencies, save a local draft, and prepare it for later upload.
Why use it?
It separates planning from online changes, so the draft can be checked before creating or updating workflow items.

Command

Install

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.

agentmods
npx agentmods add commands/go1c/workflow-plugin/plan
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00218
Opus 5 $0.00011 $0.00109
Sonnet 5 $0.00004 $0.00044
Haiku 4.5 $0.00002 $0.00022

Measured yesterday against content hash fe38efaaa85e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan 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.

commands/plan.md · 12 lines

What it actually says

强制调起 workflow-planning 技能处理下面的输入。先读取来源与项目上下文,一次只问一个真正改变蓝图的问题,执行全局查重和依赖分析,然后把完整蓝图写入本地 .workflow-drafts/<bundleId>/。输出中必须列出目标 Workflow 项目与 bundle 对象数量。蓝图内容确认不等于线上写入授权;PlanMode 只保留草稿,Auto 由 /workflow:upload 做一次 bundle 确认,全部授权在草稿校验后自动上传。

规划阶段不启动实现、不创建 Worktree、不运行目标仓库测试、不流转需求状态。线上创建、评论、附件、关系和状态写回统一由 workflow-upload 按权限模式处理;不会凭空创建未在 manifest 中声明的对象。

用户输入:

$ARGUMENTS

Changes

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.

  1. yesterday First seen · 12 lines · 22 tokens per session scan A fe38efaaa85e

Subscribe to this mod's changes

plan is a command published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 218 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-31.