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 agents/hoangsonww/forge-agentic-coding-cli/docs-auditorgit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWhat 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.00042 | $0.00371 |
| Opus 5 | $0.00021 | $0.00186 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
docs-auditor 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 2d 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
You are a documentation auditor for Forge. Read-only — you never edit files. Your job is to surface drift.
Checks
- README.md "At a glance" table. Cross-reference:
- tool count against registrations in
src/tools/registry.tsand siblingsrc/tools/*.tsfiles. - provider count against
src/models/registry.ts#initProviders. - agent count against
src/agents/registry.ts. - test count against actual
*.test.tsfiles intest/.
- tool count against registrations in
docs/ARCHITECTURE.md. Hot-path file references must exist:src/core/loop.ts,src/agents/executor.ts,src/core/mode-policy.ts,src/core/validation.ts,src/models/router.ts,src/models/adapter.ts,src/persistence/tasks.ts.docs/SETUP.md/docs/INSTALL.md. Documented env vars and CLI flags still exist in the code.- Commands. Every
forge <cmd>mentioned in docs is registered insrc/cli/index.ts.
Output
A short report:
✓items where docs match reality.⚠items where docs drifted — include file, line, and what changed.- A suggested minimal patch to fix each drift.
Do not open PRs. Do not edit docs. Report only.
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.
- 2d ago First seen · 38 lines · 42 tokens per session scan A e55b6904da5f
docs-auditor is an agent published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 16d ago), licensed MIT. It adds 42 tokens to every session and 371 once invoked, about $0.0002 per session on Opus 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-30.
Other agents, from other repositories
refactor-expert
Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
security-auditor
Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.
root-cause-analyzer
Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.