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/execute-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/execute-phase)<a href="https://agentmods.dev/commands/sairam0424/mindforge/execute-phase"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/execute-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.00018 | $0.02362 |
| Opus 5 | $0.00009 | $0.01181 |
| Sonnet 5 | $0.00004 | $0.00472 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
execute-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 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindForge — Execute Phase Command
Usage: /mindforge:execute-phase [N]
Pre-checks (all must pass before execution starts)
-
Read STATE.md — confirm phase [N] is in "planned" status. If STATE.md shows phase [N] as already "complete": ask user to confirm re-execution.
-
Verify plan files exist:
.planning/phases/[N]/PLAN-[N]-01.md (minimum one plan required)If missing: stop. Tell user: "No plans found for Phase [N]. Run /mindforge:plan-phase [N] first."
-
Verify REQUIREMENTS.md exists and has content. If empty: warn user but allow continuation.
-
Run the dependency parser (
.mindforge/engine/dependency-parser.md). If validation fails (circular deps, missing deps): stop and report. Do not execute.
Step 1 — Build and display the execution plan
After dependency parsing succeeds, display the wave plan to the user:
Phase [N] Execution Plan
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Wave 1 (parallel) Wave 2 (parallel) Wave 3
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Plan 01 │ │ Plan 03 │ │ Plan 05 │
│ User model │──┐ │ User API │──┐ │ Checkout UI │
└─────────────┘ │ └─────────────┘ │ └─────────────┘
┌─────────────┐ │ ┌─────────────┐ │
│ Plan 02 │──┘ │ Plan 04 │──┘
│ Product │ │ Product API │
└─────────────┘ └─────────────┘
Total tasks: 5 Waves: 3 Est. time: depends on model speed
Proceed? (yes/no)
If the user says no: stop. Do not execute anything.
Step 2 — Write pre-execution audit entry
Append to .planning/AUDIT.jsonl:
{
"id": "[uuid-v4]",
"timestamp": "[ISO-8601]",
"event": "phase_execution_started",
"phase": [N],
"wave_count": [total waves],
"task_count": [total tasks],
"agent": "mindforge-orchestrator",
"session_id": "[session identifier]"
}
Step 3 — Execute waves using the wave executor
Follow the complete protocol in .mindforge/engine/wave-executor.md.
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.
- yesterday First seen · 242 lines · 18 tokens per session scan A 58a7475ee648
execute-phase is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 2,362 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.
Other commands, from other repositories
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
factory-sweep
Find Linear tickets that have gone obsolete (duplicate, already shipped, overtaken by events) and retire them with evidence.
vichu
Start or continue a verified VichuFlow run for a task.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.