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 skills add movahedan/monobun --skill planning-workflowgit clone --depth 1 https://github.com/movahedan/monobunWrote 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/skills/movahedan/monobun/planning-workflow)<a href="https://agentmods.dev/skills/movahedan/monobun/planning-workflow"><img src="https://agentmods.dev/badge/skills/movahedan/monobun/planning-workflow/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/skills/movahedan/monobun/planning-workflow"><img src="https://agentmods.dev/badge/skills/movahedan/monobun/planning-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01480 |
| Opus 5.5 | $0.00025 | $0.00592 |
| Sonnet 5.5 | $0.00012 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
planning-workflow 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 2mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning workflow
When to use
- Work spans multiple packages/apps, repo layout, renames, or non-trivial tradeoffs.
- User wants plan first, phases, one PR per phase, or agent orchestration later.
- Requirements need testable gates and explicit out-of-scope before edits.
When not to use: single-file fix with obvious AC — state AC + one verify command in chat only.
Next step after approval: initiative-workflow — builder-workflow → documentation-sync → git-pr-workflow per phase.
Principles
- Repo-grounded —
Read/rg/Globbefore inventing paths; list assumptions and open questions. - Planning gate — no bulk implementation until the user approves the plan (or says execute).
- Phased increments — each phase = one mergeable unit with its own verification block.
- Hard constraints per phase — what must / must not change in that phase only (defers later renames).
- Explicit non-goals — limit scope creep; optional work labeled optional.
Phase 0 — Orient
Read root AGENTS.md, relevant package AGENTS.md, and scoped .cursor/rules/ (standards only — workflows live in skills).
Produce a short impact sketch: workspaces, config roots (package.json, turbo.json, CI, docker, bunfig.toml), docs/skills, tests.
Phase 1 — Design agreement (chat or short doc)
Align with the user:
| Topic | Capture |
|---|---|
| Outcome | What is true when done? |
| Phases | Count, order, one PR per phase? |
| Constraints | Policies that must hold every phase |
| Acceptance | Pass/fail checks per phase |
| Non-goals | Directories, renames, features off |
| Risks | What breaks first; grep/command mitigations |
Phase 2 — Write the plan file
Primary artifact: .cursor/plans/<kebab-slug>.plan.md
Use the structure in plan-template.md. Strong plans include:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 146 lines · 62 tokens per session scan A 1ece02d78a70
planning-workflow is a skill published in the GitHub repository movahedan/monobun (18 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,480 once invoked, about $0.0002 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.
planning-workflow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planning-workflowmovahedan/monobun | Skill | 18 | today | MIT | A | 62 | Claude Code, Cursor |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |