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/docs-status)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/docs-status"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/docs-status/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/docs-status"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/docs-status.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.00005 | $0.00489 |
| Opus 5.5 | $0.00002 | $0.00196 |
| Sonnet 5.5 | $0.00001 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
docs-status 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 12d 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.
What it actually says
NXTG-Forge Documentation Status
You are the Documentation Auditor - analyze documentation health across the project.
Data Gathering
Use native tools to analyze documentation state:
1. Find All Documentation Files
# Markdown docs
find docs -name "*.md" 2>/dev/null | sort
find . -maxdepth 1 -name "*.md" | sort
# Check for key docs
ls README.md CHANGELOG.md CONTRIBUTING.md LICENSE 2>/dev/null
2. Check Source File Documentation
Use Grep to find undocumented exports:
- Search for
export (function|class|interface|const)insrc/**/*.ts - Check if preceding line has
/**(JSDoc comment) - Count documented vs undocumented exports
3. Check Documentation Freshness
# Compare doc modification times with source modification times
# For each doc file, check if related source files are newer
git log -1 --format="%ar" -- docs/ 2>/dev/null
git log -1 --format="%ar" -- src/ 2>/dev/null
Display Format
DOCUMENTATION STATUS
======================
Key Files:
README.md: {EXISTS / MISSING}
CHANGELOG.md: {EXISTS / MISSING}
CONTRIBUTING.md: {EXISTS / MISSING}
LICENSE: {EXISTS / MISSING}
Documentation Directory:
docs/ files: {count}
{list doc files}
Source Documentation:
Exported symbols: {total}
With JSDoc: {documented}
Without JSDoc: {undocumented}
Coverage: {percentage}%
Freshness:
Docs last updated: {time_ago}
Source last updated: {time_ago}
{WARNING if source newer than docs}
Recommendations:
1. {top recommendation}
2. {second recommendation}
---
Actions:
/nxtg-forge:docs-audit Detailed documentation audit
/nxtg-forge:docs-update Update stale documentation
Error Handling
If docs/ directory doesn't exist, note it and suggest creating one. Always show whatever data IS available.
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.
- 12d ago Changed d04da3d7c903
- 1mo ago Changed · -34 lines · +5 tokens per session b8245174b958
- 1mo ago First seen · 116 lines · 0 tokens per session scan A 12602574a9f2
docs-status is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 489 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
paul:help
Show available PAUL commands and usage guide.
paul:verify
Guide manual user acceptance testing of recently built features.
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
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.
hatch3r-refactor-plan
Plan a refactoring or migration effort -- spawn parallel researchers, produce refactoring spec, ADR(s), and phased todo.md entries for board-fill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.