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/dashboard)<a href="https://agentmods.dev/commands/sairam0424/mindforge/dashboard"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/dashboard.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.00016 | $0.00785 |
| Opus 5 | $0.00008 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
dashboard 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindForge v2 — Dashboard Command
Usage: /mindforge:dashboard [--port 7339] [--open] [--stop] [--status]
Version: v2.0.0-alpha.5
Purpose
Start the MindForge real-time web dashboard — a live observability UI for the entire team. Shows execution progress, quality metrics, pending approvals, knowledge graph, and team activity without requiring CLI access.
Design
The dashboard is a localhost-only web server:
- No build step — single HTML file, no bundler, no npm packages on client
- No authentication — binding to 127.0.0.1 is the security model
- Live updates via Server-Sent Events — no WebSocket library needed
- Designed for screensharing at standups, not external access
Usage
Start the dashboard
/mindforge:dashboard
→ Dashboard running at: http://localhost:7339
→ Press CTRL+C to stop (or /mindforge:dashboard --stop)
Start and open in browser
/mindforge:dashboard --open
→ Opens http://localhost:7339 in your default browser
Custom port
/mindforge:dashboard --port 7340
→ Useful if 7339 is already in use
Stop the dashboard
/mindforge:dashboard --stop
→ Finds the running dashboard process (from PID file) and sends SIGTERM
Check dashboard status
/mindforge:dashboard --status
→ Checks if dashboard is running, shows port and PID
→ Also shows: http://localhost:7339/api/status
Dashboard pages
Activity (default)
- Phase name, auto mode status (RUNNING/PAUSED/ESCALATED/IDLE)
- Wave progress bar (tasks completed / total)
- Live AUDIT event feed with color-coded event types
- Steering input: send guidance to auto mode without touching the CLI
Quality Metrics
- Session quality score trend (last 20 sessions)
- Verify pass rate over time
- Security findings by severity (CRITICAL/HIGH/MEDIUM/LOW)
- Cost per session trend
Approvals
- All pending Tier 2/3 governance requests
- [Approve] and [Reject] buttons — no CLI needed for approval
- Tier, phase/plan, description, time since requested, expiry warning
- Recent approval history
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 · 103 lines · 16 tokens per session scan A 28545968f953
dashboard is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 785 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
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.