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/status-enhancedgit 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/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.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01174 |
| Opus 5 | $0.00000 | $0.00587 |
| Sonnet 5 | $0.00000 | $0.00235 |
| Haiku 4.5 | $0.00000 | $0.00117 |
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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:status-enhanced
Deep project dashboard with code metrics, commit heatmaps, dependency audits, and weighted health scoring across four dimensions.
| Level | L1 Vibe Coder |
| Category | Governance |
| Syntax | /forge:status-enhanced |
What It Does
/forge:status-enhanced is the heavyweight sibling of /forge:status. While the standard status command gives you a quick overview, the enhanced version runs a full seven-source analysis: complete git history with a 7-day commit activity heatmap, full test suite execution with verbose output, TypeScript compilation check, security audit via npm audit, source code metrics (lines of code, file counts, as any casts), dependency health (outdated packages, prod vs dev counts), and orchestrator data (task board, knowledge base, drift detection).
The health score uses a 100-point weighted system across four equally weighted dimensions: Tests (25 points based on pass rate), Types (25 points minus deductions per error and as any cast), Security (25 points minus deductions per vulnerability by severity), and Quality (25 points minus deductions for console statements and TODOs). This gives you a single number that tracks project trajectory over time.
Without this command, building the same picture would require running your test suite, type checker, and security auditor separately, counting code metrics manually, and checking npm outdated -- then doing the mental math to weight the results. The enhanced dashboard does all of this and ends with prioritized recommendations based on your lowest-scoring dimension.
Syntax & Options
/forge:status-enhanced
This command takes no arguments. It always runs the full analysis.
When to Use It
- Weekly health review: Run it once a week to track trends in code quality, test coverage, and dependency health.
- Sprint retrospective: Generate a comprehensive snapshot of where the project stands at sprint boundaries.
- Before a major refactor: Establish a baseline so you can measure the impact of architectural 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.
- 4d 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 (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,174 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
evidence
Export a signed compliance evidence package as JSON or PDF for regulatory handoff.
init-project
Configure the baseline for this specific project. Invokes the scout skill, then claude-automation-recommender, populates .claude/project.json, pre-creates lazy directories, re-renders swarm-worker.md from its template with any stack-specific skills appended, appends a §16 addendum to docs/init/seed.md, runs…
ai-act-incidents
Show real-world and research-demonstrated security incidents that map to a scanner dimension, EU AI Act article, or threat category. Surfaces OWASP LLM/ASI, NIST AI RMF, and MITRE ATLAS cross-references alongside published mitigations.
init-project-doctor
Detect and repair baseline drift — missing or invalid .claude/workflows.jsonl, schema violations, four-way Article IV / §18 mirror drift, and (advisory) shipped-tooling files placed outside .claude/ against the convention codified at seed.md §3. Interactive: presents each detected violation via AskUserQuestion and…
grant-commit
Grant consent for Claude to run git commit. Workflow-scoped when a workflow is active, else a time window. Required by the Git Commit Guard hook.
approve-direction
Record human approval of a workflow's direction (the intake + its acceptance criteria + the CO-A evidence). The Direction Approval Guard hook blocks Claude from ever writing approval tokens; this command is the only sanctioned path. Must be user-invoked. Replaces the retired /approve-spec gate (D3/CO-E gate-collapse)…