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/command-centergit 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.01241 |
| Opus 5 | $0.00000 | $0.00620 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
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 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:command-center
The canonical four-option mission control menu providing intelligent project orchestration: continue work, plan features, soundboard strategy, or run health checks.
| Level | L2 Pro Builder |
| Category | Governance |
| Syntax | /forge:command-center |
What It Does
/forge:command-center is the command you run when you sit down and ask "what should I work on?" It presents a four-option menu -- Continue/Resume, Review & Plan Features, Soundboard, and Health Check -- each backed by real data from both local state and the forge-orchestrator. Before showing the menu, it runs a pre-flight check: governance.json exists, git is initialized, and the orchestrator connection is verified.
Option 1 (Continue) restores your full context: governance directive, recent git activity, uncommitted work, saved checkpoints, AND the orchestrator task board showing pending, in-progress, and blocked tasks plus drift detection. Option 2 (Plan Features) lets you design new work with access to the existing master plan and task decomposition from the orchestrator. Option 3 (Soundboard) opens a strategic discussion grounded in real project data. Option 4 (Health Check) runs a comprehensive health analysis equivalent to /forge:gap-analysis.
The command also handles natural language input. Instead of typing "1", you can say "let's keep going" or "how are we doing?" and it maps your intent to the right option.
Syntax & Options
/forge:command-center
This command takes no arguments. It presents an interactive menu.
When to Use It
- Session start: The ideal first command when you do not know where to begin. It gathers context and presents options.
- Context recovery: After a break, compaction, or context switch, use it to restore your bearings.
- Decision point: When you have finished a task and need to decide what comes next.
For a non-interactive status overview, use /forge:status. For going directly into feature development, use /forge:feature.
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 · 126 lines · 0 tokens per session scan A 21eb8679dd2a
command-center 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,241 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
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.