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/nxtg-ai/forge-plugin/dashboardgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00975 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:dashboard
Open the visual governance dashboard in your browser -- a self-contained HTML snapshot of project health, metrics, and status powered by Tailwind CSS.
| Level | L3 Ship Lord |
| Category | Governance |
| Syntax | /forge:dashboard |
What It Does
/forge:dashboard generates and opens a visual HTML dashboard in your browser. The dashboard is created by the governance MCP server's forge_open_dashboard tool, which reads live project data (health scores, governance state, git status, code metrics) at generation time and produces a self-contained HTML file with Tailwind CSS styling. No running server is required -- it is a static snapshot that opens as a local file.
The dashboard shows your project name, health score with letter grade, and detailed metrics in a visually designed interface. It works across platforms: on WSL2 it opens via the Windows browser, on macOS via the default browser, and on Linux via xdg-open. If auto-open fails, the command displays a clickable file URL you can copy into your browser.
Without this command, visualizing project health means reading terminal output from /forge:status and mentally mapping numbers to a picture. The dashboard gives you an at-a-glance visual representation that is easier to scan, share with stakeholders, and screenshot for reports.
Syntax & Options
/forge:dashboard
This command takes no arguments. It generates and opens the dashboard.
When to Use It
- Stakeholder demos: Open the dashboard to show project health visually instead of sharing terminal output.
- Team standups: Display the dashboard on a shared screen for a quick visual status check.
- Personal orientation: When you want a graphical overview instead of a text-based one.
For text-based status that stays in the terminal, use /forge:status. For the full React-based dashboard with real-time updates and the Infinity Terminal, install forge-ui and visit localhost:5050.
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.
- 2d ago First seen · 92 lines · 0 tokens per session scan A 2aa33ef56826
dashboard is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 975 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-08-31.
Other commands, from other repositories
review-synthesize
Produce one evidence-based verdict, write the review report humans read, and publish it when the scope is a PR. You are read-only: never modify project files or commit; your only write outside the artifacts directory is the PR comment below. Read-only extends past the repository: a falsifying command creates its own…
triage
Confirm whether the work item still names real current work, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you finish. No one watches the run; the report and your…
paul:help
Show available PAUL commands and usage guide.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
paul:verify
Guide manual user acceptance testing of recently built features.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…