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 agentmods add commands/sairam0424/mindforge/plan-phasegit clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/sairam0424/mindforge/plan-phase)<a href="https://agentmods.dev/commands/sairam0424/mindforge/plan-phase"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/plan-phase.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
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 today.
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.
What it actually says
Plan a phase of the project. Usage: /forge:plan-phase [N]
If N is not provided, check STATE.md for the current phase and use that.
Steps:
- Read PROJECT.md, REQUIREMENTS.md, and STATE.md.
- Ask the user: "Describe what phase [N] should accomplish in 2-3 sentences."
- Ask: "Are there any specific implementation decisions you've already made for this phase?"
- Spawn a research subagent: Read the project's tech stack from PROJECT.md and research the best patterns, libraries, and pitfalls for implementing this phase. Write findings to
.planning/phases/phase-[N]/RESEARCH.md. - Create 3-6 atomic task plans in
.planning/phases/phase-[N]/. Each PLAN file must use this XML format:
<plan>
<task>Task name</task>
<files>
specific/file/paths/to/touch.ts
</files>
<instructions>
Precise implementation instructions. Include:
- Which library to use and why (mention specific version if relevant)
- Any gotchas or anti-patterns to avoid
- The exact approach, not just "implement X"
</instructions>
<verify>Specific command or check that confirms this task is done</verify>
<done>One sentence definition of done for this task</done>
</plan>
- Check each plan against REQUIREMENTS.md. If a plan implements something out of scope, revise it.
- Update STATE.md: current phase = N, status = "Phase [N] planned, ready to execute"
- Tell the user: "Phase [N] has [X] task plans ready. Run /forge:execute-phase [N] to begin execution."
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.
- today First seen · 31 lines · 0 tokens per session scan A 2da65b6dff32
plan-phase is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 tokens. 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.
Other commands, from other repositories
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
research-close
Close research - moves to done.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-next
Recommend and optionally run the next factory stage for this repo.
ah
Show Aigon commands (shortcut for help).
decompose
Feature/story breakdown — consume a ready-for-decompose scope doc and produce a task graph in the issue tracker. Re-entrant; tracker-as-canonical with vault breadcrumb.