mindforge-plan-phase

mindforge-plan-phase is a skill for Claude Code from sairam0424/MindForge. It costs 16 tokens per session (399 once invoked), scanned A, original, MIT.

A workflow for creating a detailed plan for one project phase, including research, checks, and acceptance criteria. It can also use an existing requirements document or close gaps found during verification.

In plain words
What is it for?
Use it to research a phase, generate a PLAN.md file, verify the plan, incorporate review feedback, or plan directly from a PRD, which is a product requirements document.
Why use it?
It turns a broad phase into checked, actionable work and reduces planning errors before implementation begins.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to research a phase, generate a PLAN.md file, verify the plan, incorporate review feedback, or plan directly from a PRD, which is a product requirements document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sairam0424/mindforge/mindforge-plan-phase
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.

Any agent
npx skills add sairam0424/MindForge --skill mindforge-plan-phase
Clone the repo
git clone --depth 1 https://github.com/sairam0424/MindForge

Made for: Claude Code.

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

agentmods badge for mindforge-plan-phase

README.md
[![agentmods](https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-plan-phase/github.svg)](https://agentmods.dev/skills/sairam0424/mindforge/mindforge-plan-phase)
Your own site
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-plan-phase"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-plan-phase/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.

agentmods 80×15 button for mindforge-plan-phase

Your own site · 80×15
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-plan-phase"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-plan-phase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 399 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00016 $0.00399
Opus 5 $0.00008 $0.00199
Sonnet 5 $0.00003 $0.00080
Haiku 4.5 $0.00002 $0.00040

Measured 6d ago against content hash 437018a82a6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mindforge-plan-phase 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 6d 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.

.agent/skills/mindforge-plan-phase/SKILL.md · 39 lines

What it actually says

Default flow: Research (if needed) → Plan → Verify → Done

Orchestrator role: Parse arguments, validate phase, research domain (unless skipped), spawn mindforge-planner, verify with mindforge-plan-checker, iterate until pass or max iterations, present results.

<execution_context> @.agent/workflows/mindforge-plan-phase.md @docs/References/ui-brand.md </execution_context>

Flags:

  • --research — Force re-research even if RESEARCH.md exists
  • --skip-research — Skip research, go straight to planning
  • --gaps — Gap closure mode (reads VERIFICATION.md, skips research)
  • --skip-verify — Skip verification loop
  • --prd <file> — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
  • --reviews — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by /mindforge-review)
  • --ads — Use Adversarial Decision Synthesis (Architect vs Auditor) for high-fidelity planning
  • --text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)

Normalize phase input in step 2 before any directory lookups.

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. 6d ago First seen · 39 lines · 16 tokens per session scan A 437018a82a6f

Subscribe to this mod's changes

mindforge-plan-phase is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 399 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-09-03.