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/docs-auditgit 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.01215 |
| Opus 5 | $0.00000 | $0.00607 |
| Sonnet 5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:docs-audit
Comprehensive documentation quality audit covering JSDoc coverage, key file inventory, link validation, code example verification, and freshness scoring.
| Level | L1 Vibe Coder |
| Category | Documentation |
| Syntax | /forge:docs-audit |
What It Does
/forge:docs-audit is the deep documentation quality assessment. It runs five audit dimensions: coverage analysis (what percentage of exported symbols have JSDoc), file inventory (which key files like README, CHANGELOG, CONTRIBUTING, and LICENSE exist), link validation (do internal markdown links point to real files), code example validation (do code blocks in docs reference existing functions and files), and freshness scoring (how recently were docs updated relative to source).
The output is a multi-score report: Coverage %, Completeness %, Freshness %, and Link Health %, plus an overall average. Each dimension lists specific findings -- undocumented exports, missing key files, broken links, stale pages -- so you know exactly what to fix. The issues are severity-ranked and the recommendations are prioritized by impact.
Without this command, auditing documentation quality means manually checking for broken links, eyeballing JSDoc coverage by scrolling through code, and hoping someone notices when key files are missing. /forge:docs-audit automates the entire audit and gives you concrete scores to track over time.
Syntax & Options
/forge:docs-audit
This command takes no arguments. It always runs the full five-dimension audit.
When to Use It
- Pre-release quality gate: Ensure documentation meets a minimum quality bar before tagging a release.
- New maintainer onboarding: Audit the project's documentation to identify what a new contributor would need.
- Quarterly documentation review: Run it periodically to catch documentation decay.
For a quick health check without the full audit, use /forge:docs-status. For fixing issues found by the audit, use /forge:docs-update.
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.
- 3d 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 (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,215 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
review-synthesize
Produce one evidence-based verdict, write the review report humans read, and publish it when the scope is a PR. You are read-only: never modify project files or commit; your only write outside the artifacts directory is the PR comment below. Read-only extends past the repository: a falsifying command creates its own…
triage
Confirm whether the work item still names real current work, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you finish. No one watches the run; the report and your…
paul:help
Show available PAUL commands and usage guide.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
paul:verify
Guide manual user acceptance testing of recently built features.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…