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-enhanced)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/status-enhanced"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/status-enhanced/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-enhanced"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/status-enhanced.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.01824 |
| Opus 5.5 | $0.00003 | $0.00730 |
| Sonnet 5.5 | $0.00001 | $0.00365 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
status-enhanced 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Enhanced Status Dashboard
You are the Dashboard Reporter - show a comprehensive, detailed project dashboard with metrics and recommendations.
This is the enhanced version of /nxtg-forge:status with deeper analysis.
Data Gathering
Gather ALL data using native tools in parallel:
1. Complete Git Analysis
# Branch info
git branch --show-current
git log --oneline -20
git shortlog -sn --since="30 days ago" 2>/dev/null
# Change stats
git diff --stat main...HEAD 2>/dev/null
git diff --shortstat HEAD~10..HEAD 2>/dev/null
# Activity heatmap (commits per day last 7 days)
for i in $(seq 0 6); do
date_str=$(date -d "$i days ago" +%Y-%m-%d 2>/dev/null || date -v-${i}d +%Y-%m-%d)
count=$(git log --oneline --after="$date_str 00:00" --before="$date_str 23:59" 2>/dev/null | wc -l)
echo "$date_str: $count"
done
2. Full Test Analysis
npx vitest run --reporter=verbose 2>&1
3. TypeScript Health
npx tsc --noEmit 2>&1 | tail -20
4. Security
npm audit --json 2>/dev/null | head -50
5. Code Metrics
# Total lines of code
find src -name "*.ts" -not -name "*.test.ts" -not -path "*/__tests__/*" | xargs wc -l 2>/dev/null | tail -1
# File count
find src -name "*.ts" -not -name "*.test.ts" -not -path "*/__tests__/*" | wc -l
# Test file count
find src -name "*.test.ts" -o -name "*.spec.ts" | wc -l
# Type safety
grep -rn "as any" src/ --include="*.ts" | grep -v test | grep -v __tests__ | wc -l
6. Governance & Agents
Read .claude/governance.json for governance state, or .forge/governance.json when only forge init has run. Either file means governance is initialized.
Agents and commands are loaded from the NXTG-Forge plugin. Count them in the installed plugin with this command, and use its numbers for {agent_count} and {command_count}; never a number written here. No need to check .claude/agents/ or .claude/commands/ directories.
R="${CLAUDE_PLUGIN_ROOT}"; n() { wc -l | tr -d ' '; }
echo "agents=$(ls "$R"/agents/*.md 2>/dev/null | n) commands=$(ls "$R"/commands/*.md 2>/dev/null | n) skills=$(ls "$R"/skills/*/SKILL.md 2>/dev/null | n) hooks=$(grep -o 'scripts/[A-Za-z0-9_.-]*\.sh' "$R/hooks/hooks.json" 2>/dev/null | sort -u | n) registrations=$(grep -o '"command"[[:space:]]*:' "$R/hooks/hooks.json" 2>/dev/null | n)"
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 · +11 lines b7de5b8eefde
- 12d ago Changed 2029bf7b7a29
- 1mo ago Changed · +70 lines · +7 tokens per session 9b05d89cd89f
- 1mo ago First seen · 100 lines · 0 tokens per session scan A 730664e91015
status-enhanced 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,824 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-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.
hatch3r-onboard
Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…