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-audit)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/docs-audit"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/docs-audit/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-audit"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/docs-audit.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.00724 |
| Opus 5.5 | $0.00002 | $0.00290 |
| Sonnet 5.5 | $0.00001 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
docs-audit 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Documentation Audit
You are the Documentation Auditor - perform a comprehensive quality audit of all project documentation.
Audit Dimensions
Run all checks using native tools:
1. Coverage Analysis
Use Grep and Glob to measure:
- Count all exported symbols in
src/**/*.ts(excluding tests) - Count which have JSDoc/TSDoc comments
- Calculate documentation coverage percentage
# Count exports
grep -rn "^export " src/ --include="*.ts" | grep -v test | grep -v __tests__ | wc -l
# Count documented exports (preceded by /** ... */)
2. File Inventory
# All documentation files
find . -name "*.md" -not -path "*/node_modules/*" -not -path "*/.git/*" | sort
# Key files check
for f in README.md CHANGELOG.md CONTRIBUTING.md LICENSE; do
[ -f "$f" ] && echo "EXISTS: $f" || echo "MISSING: $f"
done
3. Link Validation
Use Grep to find markdown links and verify they point to existing files:
# Find all internal links in docs
grep -rn '\[.*\](\..*\.md)' docs/ --include="*.md" 2>/dev/null
For each link, verify the target file exists.
4. Code Example Validation
Find code blocks in docs and check if they reference existing functions/files:
grep -A5 '```typescript' docs/**/*.md 2>/dev/null
5. Freshness Check
# Find oldest documentation files
find docs -name "*.md" -exec stat --format="%Y %n" {} \; 2>/dev/null | sort -n | head -10
Audit Report
DOCUMENTATION AUDIT REPORT
=============================
Generated: {timestamp}
SCORES
Coverage: {pct}% ({documented}/{total} exports)
Completeness: {pct}% ({existing}/{expected} key files)
Freshness: {pct}% ({current}/{total} docs up-to-date)
Link Health: {pct}% ({valid}/{total} links working)
Overall: {average}%
COVERAGE DETAILS
Documented exports: {count}
Undocumented exports: {count}
Files with no docs: {list}
KEY FILES
README.md: {status}
CHANGELOG.md: {status}
CONTRIBUTING.md: {status}
LICENSE: {status}
docs/API.md: {status}
FRESHNESS
Most stale: {file} (last updated {time_ago})
Most current: {file} (updated {time_ago})
ISSUES FOUND
{severity} - {description}
{severity} - {description}
...
RECOMMENDATIONS
1. [{priority}] {recommendation}
2. [{priority}] {recommendation}
3. [{priority}] {recommendation}
---
Actions:
/nxtg-forge:docs-update Fix stale docs
/nxtg-forge:docs-update --jsdoc Add missing JSDoc
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 26e303d786c5
- 1mo ago Changed · -13 lines · +5 tokens per session 410b036abe56
- 1mo ago First seen · 123 lines · 0 tokens per session scan A 54d3826126e7
docs-audit 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 724 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.