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 initiative-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/initiative-workflow)<a href="https://agentmods.dev/skills/movahedan/monobun/initiative-workflow"><img src="https://agentmods.dev/badge/skills/movahedan/monobun/initiative-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/initiative-workflow"><img src="https://agentmods.dev/badge/skills/movahedan/monobun/initiative-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.00048 | $0.00968 |
| Opus 5.5 | $0.00019 | $0.00387 |
| Sonnet 5.5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
initiative-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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initiative workflow
End-to-end order for a planned feature in this repo. Each step uses one skill; do not merge steps into one mega-prompt.
flowchart LR
P[planning-workflow]
B[builder-workflow]
D[documentation-sync]
G[git-pr-workflow]
P --> B --> D --> G
Repeat B → D → G for each plan phase (each PR).
Step 1 — Product context (optional)
When: Outcome or UX is still fuzzy.
How: Short chat (or brainstorming skill from superpowers cache) — problem, users, constraints, non-goals.
Output: Bullets the planner pastes into the plan’s summary / Phase 1 design agreement. Not a substitute for the plan file.
Step 2 — planning-workflow
When: Multi-package work, phases, or “plan first.”
Output: .cursor/plans/<slug>.plan.md (approved by you).
Plan must include per phase:
| Section | Owner skill |
|---|---|
| Code/config surfaces, scouts, verify commands | builder-workflow |
| Documentation before PR (path list) | documentation-sync — after build, not during |
Your message (minimal):
Use planning-workflow.
Goal: …
Constraints: …
Phases: … (one PR per phase if applicable)
Step 3 — builder-workflow (per phase)
When: Plan approved; execute one phase.
Scope: Code and config only — no docs/, AGENTS.md, README.md, .cursor/skills/ edits unless the plan labels a docs-only phase.
Ends at: Checkup PASS + code review critical fixes fixed. Does not commit (unless you explicitly ask).
Your message (minimal):
@.cursor/plans/<slug>.plan.md
Use builder-workflow. Execute Phase N only.
Do not edit documentation tiers; those are step 4.
Do not attach: rules bodies, full product spec, scout tables from prior runs.
Step 4 — documentation-sync (per phase, before PR)
When: Phase build is finished (verify gate passed on code/config). Before any commit or PR for that phase.
Not: During scout/implement/checkup. Not interleaved with implementer slices.
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 · 124 lines · 48 tokens per session scan A 00ffb0ff5fb1
initiative-workflow is a skill published in the GitHub repository movahedan/monobun (18 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 968 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.
initiative-workflow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| initiative-workflowmovahedan/monobun | Skill | 18 | today | MIT | A | 48 | 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 |