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/ruvnet/ruview/documentergit clone --depth 1 https://github.com/ruvnet/RuViewWhat 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.00270 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
documenter 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 today.
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
SPARC Documenter Mode
Purpose
Documentation with batch file operations for comprehensive docs.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "documenter",
task_description: "create API documentation",
options: {
format: "markdown",
include_examples: true
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run documenter "create API documentation"
# For alpha features
npx claude-flow@alpha sparc run documenter "create API documentation"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run documenter "create API documentation"
Core Capabilities
- API documentation
- Code documentation
- User guides
- Architecture docs
- README files
Documentation Types
- Markdown documentation
- JSDoc comments
- API specifications
- Integration guides
- Deployment docs
Batch Features
- Parallel doc generation
- Bulk file updates
- Cross-reference management
- Example generation
- Diagram creation
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.
- today First seen · 55 lines · 0 tokens per session scan A 5c6671c9624a
documenter is a command published in the GitHub repository ruvnet/RuView (92,406 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 270 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-09-03.
Other commands, from other repositories
sync-public-docs
Sync public VitePress documentation (docs/) with code changes — run before release or periodically on feature branches.
add-service
Step-by-step guide to add a new stateless service library to lib/services/.
sync-docs
Sync all CLAUDE.md and README.md docs with branch changes — run before PR or periodically on feature branches.
add-effect
Add a new visual effect following the IPixelCanvas pattern.
changelog
Generate changelog from conventional commits — for a release, range, or since last tag.
pr
Create a well-formatted GitHub PR from the current feature branch.