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/init-projectgit 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/init-project)<a href="https://agentmods.dev/commands/sairam0424/mindforge/init-project"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/init-project.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.00305 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
init-project 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
Initialize a new project under the FORGE framework.
Follow these steps in order:
-
Ask the user these questions one at a time (wait for each answer before asking the next):
- What is this project? (1-2 sentence description)
- Who is the target user?
- What is the core problem it solves?
- What tech stack do you want to use? (or "help me decide")
- What is absolutely NOT in scope for v1?
- What does success look like at the end of v1?
-
If the user said "help me decide" on tech stack, ask 3 clarifying questions then recommend a stack with brief reasoning.
-
Create
.planning/PROJECT.mdwith:- Project name and one-line description
- Problem statement
- Target user
- Tech stack (with brief rationale for each choice)
- v1 scope (what's in)
- Out of scope (what's explicitly not in v1)
- Success criteria
-
Create
.planning/STATE.mdwith:- Status: Project initialized
- Current phase: None (not started)
- Last action: Project initialization
- Next step: Run /forge:plan-phase 1
-
Create
.planning/REQUIREMENTS.md(blank template with sections) -
Tell the user: "Project initialized. Run /forge:plan-phase 1 to begin planning your first phase."
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 · 33 lines · 0 tokens per session scan A 9ae43ba1dd59
init-project 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 305 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.