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.
git 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/discuss-phase)<a href="https://agentmods.dev/commands/sairam0424/mindforge/discuss-phase"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/discuss-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.1 | $0.00007 | $0.01259 |
| Opus 5 | $0.00003 | $0.00629 |
| Sonnet 5 | $0.00001 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
discuss-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 4d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindForge — Discuss Phase Command
Usage: /mindforge:discuss-phase [N] [--batch] [--auto]
Captures implementation decisions before planning begins.
Run this BEFORE /mindforge:plan-phase for complex phases.
Purpose
Planning without discussion produces generic plans. Discussion captures YOUR decisions — layout preferences, library choices, UX specifics, edge cases you've already thought through — so the planner builds what you actually want, not what seems reasonable.
When to use
- Any phase with UI/UX components (visual decisions need capturing)
- Any phase with multiple valid implementation approaches
- Any phase where you already have opinions on the approach
- Any phase touching external services (your preferences on APIs matter)
- Skip for trivial phases (e.g., "add one field to an existing form")
Step 1 — Analyse the phase scope
Read:
- ROADMAP.md for the phase description
- REQUIREMENTS.md for the requirements in this phase
- ARCHITECTURE.md for relevant architectural context
Identify the phase's primary domain and any secondary domains. If multiple domains are involved, cover each relevant set of questions.
- Visual/UI → ask about layout, interactions, states, empty states, animations
- API/Backend → ask about response format, error handling, auth approach, versioning
- Data/Database → ask about schema design, migration strategy, data volume expectations
- Integration → ask about third-party API choices, error recovery, retry strategy
- Infrastructure → ask about deployment strategy, scaling approach, observability
Step 2 — Structured discussion
Ask questions ONE AT A TIME. Wait for the full answer before asking the next.
Do not batch questions (unless --batch flag is provided).
Visual/UI phases — ask about:
- "Walk me through what a user sees on this screen from top to bottom."
- "What does the empty state look like? (nothing loaded yet / no results / error)"
- "Any animations or transitions you're picturing? Or keep it static?"
- "On mobile — stacks vertically or anything different?"
- "Any edge cases? (very long text, images that fail to load, loading states)"
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.
- 4d ago First seen · 143 lines · 7 tokens per session scan A defa06dbec08
discuss-phase is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 1,259 once invoked, about $0.0000 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
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
p3-infra-monitoring
Defines logging, metrics, alerting and error tracking.
p3-infra-teststrategy
Defines test levels, test tools, coverage targets and critical test paths.
gate-p1
Checks whether all results of the conception phase are complete and robust, and prepares the transition to the validation phase. No argument – this gate always checks the complete checklist.
p6-a11y
Systematically checks the application for accessibility. Each A11y dimension is a separate sub-command.