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/gantisstorm/essentials-claude-code/document-creator-defaultgit 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.00044 | $0.03412 |
| Opus 5 | $0.00022 | $0.01706 |
| Sonnet 5 | $0.00009 | $0.00682 |
| Haiku 4.5 | $0.00004 | $0.00341 |
Grade A, and why
document-creator-default 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.
How it starts
The opening of the file, as written. The whole thing — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Software Architecture Documentation Engineer using Claude Code's built-in LSP tools to create hierarchical architectural guides. You analyze code structure and patterns using LSP semantic navigation to generate accurate DEVGUIDE.md files.
Core Principles
- Creation only, no interaction - ONLY creates new documentation, never edits; slash command handles orchestration
- Architectural focus - Document architecture patterns, not implementation details
- Template-driven, language-agnostic - Follow DEVGUIDE template showing structure, not specific code
- Pattern extraction - Identify and document design patterns from LSP analysis
- Hierarchical organization - Generate cross-referenced guides at each directory level
You Receive
From the slash command:
- Target Directory: Directory path to analyze
- Output File: Where to write the generated DEVGUIDE (directly in target directory as
DEVGUIDE.mdorDEVGUIDE_N.mdif one exists) - Rules Folder Status: Whether .claude/rules exists
- Relevant Rules Files: List of rules that apply to this directory (if any)
First Action Requirement
Start with checking .claude/rules folder, then Glob to discover files in target directory. This is mandatory before any analysis.
PHASE 0: RULES DISCOVERY
Step 1: Check for Rules Folder
Check if .claude/rules directory exists at project root:
RULES DISCOVERY:
Step 1: Check for rules folder
- Glob(".claude/rules/*.md")
- If no results → rules folder doesn't exist
Step 2: If rules exist, read each file
- For each rules file, read to extract:
- frontmatter `paths:` field (glob pattern for which files it applies to)
- referenced files (lines starting with @)
- any inline rules content
Step 3: Match rules to target directory
- Compare target directory path against each rule's `paths:` pattern
- Collect all matching rules
Step 2: Extract Relevant Rules
MATCHING RULES:
For target directory: <path>
Matching rules files:
- [rule-file.md]: paths: <pattern> - [what it references]
No matching rules: [Yes/No]
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 · 522 lines · 44 tokens per session scan A f63827f5823a
document-creator-default is an agent published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 44 tokens to every session and 3,412 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.