status

A project-status command that collects project metadata, Git history, test results, governance, task-board data, build output, available tools, and health scores into one formatted dashboard. It can also return selected sections or JSON.

In plain words
What is it for?
Use it at the start of a coding session to inspect Git state, tests, governance, builds, tasks, available agents and commands, and overall project health.
Why use it?
It gives you a starting view of an unfamiliar or long-running project without gathering status from many places yourself. Health scores and a letter grade provide a quick summary of areas needing attention.

Command

Install

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.

agentmods
npx agentmods add commands/nxtg-ai/forge-plugin/status
Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,330 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01330
Opus 5 $0.00000 $0.00665
Sonnet 5 $0.00000 $0.00266
Haiku 4.5 $0.00000 $0.00133

Measured 2d ago against content hash 8aa42aad0555, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

status 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.

docs/commands/status.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/forge:status

Display complete project health in a single styled dashboard -- git state, health scores with progress bars, tests, governance, orchestrator, and tooling inventory.

Level L1 Vibe Coder
Category Governance
Syntax /forge:status [--json] [--git] [--tests] [--governance] [--verbose]

What It Does

/forge:status is the zero-context-friendly command you run at the start of every session. It gathers data from eight sources in parallel -- project metadata, git history, test results, governance state, orchestrator task board, build output, agent/command/hook inventory, and health scores -- then renders a richly formatted markdown dashboard with progress bars, tables, and color-coded headers.

The health section is the centerpiece: five dimensions (Tests, Types, Security, Docs, Project) are scored against their actual point maximums and displayed as 20-character Unicode progress bars. An overall letter grade (A through F) gives you an instant read on project health. Every section uses pipe-delimited markdown tables that render with borders, bold text, and color in Claude Code's TUI.

Without this command, you would need to run git status, git log, your test runner, your type checker, npm audit, and manually inspect governance files -- then mentally combine the results. /forge:status does all of that in one invocation and ends with an interactive menu that turns the dashboard from a dead-end into a launchpad for your next action.

Syntax & Options

/forge:status [--json] [--git] [--tests] [--governance] [--verbose]
Option Description
--json Output all gathered data as a JSON object instead of formatted text; skips the interactive menu
--git Show only the git section with expanded log and diff stats
--tests Show only the test section with full test runner output
--governance Show only the governance section with the complete sentinel log
--verbose Show all sections with additional detail

Read the full file on GitHub · 107 lines

Changes

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.

  1. 2d ago First seen · 107 lines · 0 tokens per session scan A 8aa42aad0555

Subscribe to this mod's changes

status is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,330 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.