Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nxtg-ai/forge-plugin/plugin install nxtg-forgeWrote 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/nxtg-ai/forge-plugin/status)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/status"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/status"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/status.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01673 |
| Opus 5.5 | $0.00004 | $0.00669 |
| Sonnet 5.5 | $0.00002 | $0.00335 |
| Haiku 4.5 | $0.00001 | $0.00167 |
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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Status
You are the Status Reporter - show complete project state in a zero-context-friendly format.
The report (computed by code, already run)
!node "${CLAUDE_PLUGIN_ROOT}/scripts/status-report.mjs"
The output above is the status report, computed by scripts/status-report.mjs: the report is the block between <!-- forge-required: status v1 --> and <!-- /forge-required -->, and after it come two machine lines, orchestrator=<state> and json=, which carries the same data as JSON. The block opens with an executive summary (verdict, health score and grade, the three findings that matter now), then what changed since the last run, Git, Health, Tests, Governance, Orchestrator, Tooling, next actions with their commands, and provenance. The script read the project's git state, computed the health score and grade with the same function that serves forge_get_governance_health, counted the tests, read governance, and asked the orchestrator itself for its line (it started the plugin's orchestrator server, listed its tools and called forge_get_state).
Start your reply with that block, printed exactly as given: every line, in order, as real markdown (not in a code block). Never print the orchestrator= line, and never print the json= line unless --json was given. You may leave out the two marker comments. Do not reword, reorder, round, summarize or skip any line, and do not decide the orchestrator's state yourself from any tool result. A Stop check compares your reply with the block line by line; the turn cannot end until every line is there. The orchestrator= value is the --json "orchestrator" value.
If the output above is empty or has no <!-- forge-required: status v1 --> block (the step did not run), print exactly ◌ **Forge status unavailable** — the status step did not run instead, and use "orchestrator": "unavailable" in --json. Never decide the state from tool results instead. Never estimate a health score.
After the report (optional sections)
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 Changed 9edbd6f939ff
- 6d ago Changed · -148 lines scan C → A 8595e8077922
- 7d ago Changed · +6 lines a11666998eef
- 12d ago Changed · +4 lines 65c5270192f3
- 1mo ago Changed · +101 lines · +9 tokens per session scan A → C 2d6d48f2f074
- 1mo ago First seen · 107 lines · 0 tokens per session scan A 8aa42aad0555
status is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 1,673 once invoked, about $0.0000 per session on Opus 5.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-08-31.
Other commands, from other repositories
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
paul:add-phase
Add a new phase to current milestone.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
hatch3r-roadmap
Sequence delivery phases over time into a dependency-ordered milestone plan with business and technical lenses, emitting a todo.md rollout schedule rather than design docs.
hatch3r-migration-plan
Create a phased migration plan for a major dependency or framework upgrade. Analyzes breaking changes and produces an actionable plan with rollback procedures.