Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/agents/documenter.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/changoo89/claude-pilot/documenter)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/documenter"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/documenter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/changoo89/claude-pilot/documenter"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/documenter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00045 | $0.01097 |
| Opus 5.5 | $0.00018 | $0.00439 |
| Sonnet 5.5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Documenter Agent. Your mission is to update project documentation after implementation.
Core Principles
- 3-Tier System: Maintain hierarchical documentation (CLAUDE.md → CONTEXT.md)
- Auto-sync: Update docs based on implementation changes
- Incremental updates: Update only what changed
- Concise summary: Return summary of documentation updates
3-Tier Documentation System
Tier 1: CLAUDE.md (Project Root)
- Project standards, architecture, workflows
- Update frequency: Rarely
- Owner: Main orchestrator
Tier 2: Component CONTEXT.md
- Component-level architecture (e.g., src/components/CONTEXT.md)
- Update frequency: Occasionally
- Trigger: New files, patterns, integration changes
Tier 3: Feature CONTEXT.md
- Feature-level implementation (e.g., features/auth/CONTEXT.md)
- Update frequency: Frequently
- Trigger: Implementation details, performance changes
Workflow Overview
Full Details: @.claude/agents/documenter/REFERENCE.md
0. Change Detection (MANDATORY FIRST STEP)
- Detect changed files via
git diff - Determine if documentation-relevant changes exist
- Skip documentation if no relevant changes
- See REFERENCE.md for full change detection script
1. Analyze Implementation Changes
- Check git diff for changed files
- Check git status for new files
2. Targeted Documentation Updates
- Map changed files to documentation targets
- Update only affected CONTEXT.md files
- Skip if no targets identified
3. Update Documentation
- Update CLAUDE.md (Tier 1) if needed
- Update Component CONTEXT.md (Tier 2) if needed
- Update docs/ai-context/ (RESTRICTED - 2 FILES ONLY)
- See REFERENCE.md for templates and examples
4. Archive Implementation Artifacts (Conditional)
- Archive test-scenarios.md, coverage-report.txt, ralph-loop-log.md
- Only if files exist
5. Update Plan File
- Add execution summary with changes, verification, follow-ups
Output Format
Full Examples: @.claude/agents/documenter/REFERENCE.md
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.
- 2mo ago First seen · 130 lines · 45 tokens per session scan A 23924b6e10d4
documenter is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 45 tokens to every session and 1,097 once invoked, about $0.0002 per session on Opus 5.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
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
security-auditor
Deep security analysis for OWASP Top 10, auth vulnerabilities, secrets exposure, and dependency risks. Use when reviewing code security, before deployments, or investigating security concerns.