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/gantisstorm/essentials-claude-code/document-creatorgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00013 | $0.00697 |
| Opus 5 | $0.00006 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
document-creator 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 yesterday.
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.
Document Creator
Generate hierarchical architectural documentation (DEVGUIDE.md) using Claude Code's built-in LSP tools. Supports multiple directories with parallel agent execution.
Built-in LSP Operations
documentSymbol— Extract symbols from filesfindReferences— Map dependenciesgoToDefinition— Detailed symbol analysis
Arguments
Directory paths to document (one agent per directory):
- Single directory:
/document-creator src/services/ - Multiple directories:
/document-creator src/services src/components src/lib - No argument: analyzes current directory (
.)
Instructions
Step 1: Parse Input
Parse $ARGUMENTS to extract directory list:
- Split arguments by spaces
- If empty → use current directory (
.) - Validate each path exists as a directory
Step 2: Check for Rules
Check if .claude/rules directory exists at project root:
Use Glob(".claude/rules/*.md") to find rules files.
If rules exist:
- Read each rules file to understand frontmatter paths
- Pass relevant rules info to agents
If no rules exist:
- Note this for agents to create rules files when missing
Step 3: Determine Output Paths
For each directory:
- If no DEVGUIDE.md exists →
<target-dir>/DEVGUIDE.md - If exists →
<target-dir>/DEVGUIDE_2.md(increment until unused)
Step 4: Launch Agents
For EACH directory, launch background agent:
Generate DEVGUIDE: <directory-path>
Output: <determined path>
Rules: <exists/not found>
REQUIRED Task tool parameters:
subagent_type: "essentials:document-creator-default"
run_in_background: true
prompt: "Generate DEVGUIDE: <dir>\nOutput: <path>\nRules: <status>"
Launch ALL agents in a single message for parallel execution. Output a status message like "Generating N DEVGUIDE files..." and end your turn. The system wakes you when agents finish.
Step 5: Report Results
## DEVGUIDE Documentation Created (LSP)
| Directory | Output | Status |
|-----------|--------|--------|
| [dir1] | [output path] | CREATED |
| [dir2] | [output path] | CREATED |
Rules Status: [Found N rules / No rules folder found]
Next Steps:
1. Review generated documentation
2. Commit the DEVGUIDE files
3. [If no rules] Agent created .claude/rules/ file automatically
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.
- yesterday First seen · 110 lines · 13 tokens per session scan A f670c7a45784
document-creator is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 13 tokens to every session and 697 once invoked, about $0.0001 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 commands, from other repositories
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.