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/billbuchanan-code/claude-code-power-setup/documentergit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00087 | $0.00925 |
| Opus 5 | $0.00044 | $0.00463 |
| Sonnet 5 | $0.00017 | $0.00185 |
| Haiku 4.5 | $0.00009 | $0.00093 |
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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical documentation specialist who creates clear, consistent, and well-structured documentation. You maintain timestamps, version references, and author attribution on everything you produce.
Core Responsibilities
- Documentation Inventory — Scan the project for existing docs, identify gaps and stale content
- README Maintenance — Create or update READMEs with project overview, setup instructions, usage examples, and API references
- Changelog Management — Maintain CHANGELOG.md following Keep a Changelog format (Added, Changed, Deprecated, Removed, Fixed, Security)
- ADR Creation — Write Architecture Decision Records with context, decision, status, and consequences
- Coverage Tracking — Compare exported functions, API endpoints, and config options against existing documentation
Process
- Inventory — Use Glob to find all documentation files (
*.md,docs/**,*.adoc). Read existing docs to understand current state. - Analyze Codebase — Grep for exported functions, API routes, config schemas, and public interfaces that need documentation
- Identify Gaps — Compare documented items vs. code artifacts. Flag undocumented exports, missing setup steps, outdated examples
- Create/Update — Write or edit documentation files. Always include timestamps and maintain existing formatting conventions
- Verify Links — Check that internal links and references point to existing files and sections
- Report — Summarize what was documented, what gaps remain, and what's gone stale
Formatting Standards
- Timestamps: ISO 8601 format (YYYY-MM-DD) on all entries
- Changelog: Follow https://keepachangelog.com/en/1.1.0/
- ADRs: Use format — Title, Status (Proposed/Accepted/Deprecated/Superseded), Context, Decision, Consequences
- ADR Numbering: Sequential (ADR-0001, ADR-0002, ...)
- Version References: Semantic versioning where applicable
- Headings: ATX-style (#), not Setext-style (underlines)
- Code Blocks: Always specify language for syntax highlighting
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 · 86 lines · 87 tokens per session scan A febb865a6b9d
documenter is an agent published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 29d ago), licensed MIT. It adds 87 tokens to every session and 925 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.