command-center

command-center is a command for Claude Code from nxtg-ai/forge-plugin. It costs 7 tokens per session (1,289 once invoked), scanned A, original, MIT.

A project command menu for deciding what to work on next. It checks project setup, then offers options to resume work, plan features, discuss strategy, or check project health.

In plain words
What is it for?
Use it to resume a paused task, break planned features into work, discuss project direction, or verify the project's setup and health.
Why use it?
It brings project status, saved progress, and task-board information together, so you do not have to inspect each source separately before choosing your next task.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to resume a paused task, break planned features into work, discuss project direction, or verify the project's setup and health.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nxtg-ai/forge-plugin/command-center
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.

Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

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

agentmods badge for command-center

README.md
[![agentmods](https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/command-center/github.svg)](https://agentmods.dev/commands/nxtg-ai/forge-plugin/command-center)
Your own site
<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.

agentmods 80×15 button for command-center

Your own site · 80×15
<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>
Per session 7 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,289 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.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

Measured 6d ago against content hash fdc300d70339, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/nxtg-forge/commands/command-center.md · 155 lines

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:

  1. Check that .claude/governance.json or .forge/governance.json exists (Read tool). Either one means Forge is set up: /nxtg-forge:init writes the first, forge init the second.
  2. Check NXTG-Forge plugin is loaded (commands are available -- if this command is running, the plugin is active)
  3. Check git is initialized (git rev-parse --is-inside-work-tree)
  4. 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 (run forge mcp to 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:

  1. Read .claude/governance.json for current directive and workstreams
  2. Run git log --oneline -10 for recent activity
  3. Run git status --porcelain for uncommitted work
  4. Check .claude/checkpoints/ for saved states
  5. Read any TODO items from governance sentinel log
  6. Call forge_get_tasks to get orchestrator task board (pending, in-progress, blocked)
  7. Call forge_get_plan to get master plan and current phase
  8. Call forge_check_drift to verify alignment with vision

Read the full file on GitHub · 155 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. 6d ago Changed fdc300d70339
  2. 12d ago Changed e4b8d14f9cbe
  3. 1mo ago Changed · +29 lines · +7 tokens per session c65cb06ee22b
  4. 1mo ago First seen · 126 lines · 0 tokens per session scan A 21eb8679dd2a

Subscribe to this mod's changes

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.