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/nxtg-ai/forge-pluginWrote 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/command-center)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/command-center"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/command-center/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/command-center"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/command-center.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.00007 | $0.01289 |
| Opus 5.5 | $0.00003 | $0.00516 |
| Sonnet 5.5 | $0.00001 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
command-center 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 6d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Command Center
You are activating the NXTG-Forge Command Center - the canonical 4-option menu that provides intelligent project orchestration.
Pre-flight Check
Before showing the menu, quickly verify forge is set up:
- Check that
.claude/governance.jsonor.forge/governance.jsonexists (Read tool). Either one means Forge is set up:/nxtg-forge:initwrites the first,forge initthe second. - Check NXTG-Forge plugin is loaded (commands are available -- if this command is running, the plugin is active)
- Check git is initialized (
git rev-parse --is-inside-work-tree) - Check orchestrator connection: call
forge_get_state— if it returns data, the Rust orchestrator is connected. Show "Orchestrator: CONNECTED (v{version})" or "Orchestrator: NOT CONNECTED (runforge mcpto enable)"
If neither governance.json exists, suggest: "Run /nxtg-forge:init first to set up NXTG-Forge."
Display Command Center
Present this menu to the user:
NXTG-FORGE COMMAND CENTER
===========================
What shall we accomplish today?
1. Continue / Resume
Pick up where we left off - restore context, show pending work
2. Review & Plan Features
Design and plan new work, create feature specs
3. Soundboard
Discuss strategy, get recommendations, explore options
4. Health Check
Review code quality, test coverage, security, and project metrics
Enter choice (1-4) or describe what you need:
Use AskUserQuestion to get the user's choice with these 4 options.
Handle Each Option
Option 1: Continue / Resume
Gather and display context from BOTH local state and orchestrator:
- Read
.claude/governance.jsonfor current directive and workstreams - Run
git log --oneline -10for recent activity - Run
git status --porcelainfor uncommitted work - Check
.claude/checkpoints/for saved states - Read any TODO items from governance sentinel log
- Call
forge_get_tasksto get orchestrator task board (pending, in-progress, blocked) - Call
forge_get_planto get master plan and current phase - Call
forge_check_driftto verify alignment with vision
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.
- 6d ago Changed fdc300d70339
- 12d ago Changed e4b8d14f9cbe
- 1mo ago Changed · +29 lines · +7 tokens per session c65cb06ee22b
- 1mo ago First seen · 126 lines · 0 tokens per session scan A 21eb8679dd2a
command-center is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 1,289 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.