documenter

A documentation-writing agent that updates documentation and skills to match a code change.

In plain words
What is it for?
Use it after code changes when docs or agent skills need corresponding updates. It does not write project mission statements or make architecture decisions.
Why use it?
It helps keep written instructions and reference material from falling out of sync with the code.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/retospect/precis-mcp/documenter
Clone the repo
git clone --depth 1 https://github.com/retospect/precis-mcp

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 747 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.00747
Opus 5 $0.00013 $0.00374
Sonnet 5 $0.00005 $0.00149
Haiku 4.5 $0.00003 $0.00075

Measured 2d ago against content hash 047e8aec4a8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.claude/agents/documenter.md · 53 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 53 lines · 26 tokens per session scan A 047e8aec4a8d

Subscribe to this mod's changes

documenter is an agent published in the GitHub repository retospect/precis-mcp (3 stars, last pushed 2d ago), licensed GPL-3.0. It adds 26 tokens to every session and 747 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-31.

Related

Other agents, from other repositories

reviewer

Strict read-only checker for Project 4 fix candidates.

DanielHashmi/Q4_learning · 11 tokens

opus-subagent-supervisor

Use this agent when you need to supervise and validate the execution of multiple subagents, ensuring their inputs are properly formatted, procedures are followed correctly, and outputs meet quality standards. Examples: Context: User has multiple specialized agents working on a complex task and needs oversight. user…

clchinkc/document-mcp · 229 tokens

performance-optimizer

Use this agent when you need to analyze and optimize system performance, identify bottlenecks, improve code efficiency, or enhance application speed. Examples: Context: User has written a function that processes large datasets but is running slowly. user: 'This data processing function is taking too long to execute'…

clchinkc/document-mcp · 199 tokens

code-refactoring-specialist

Use this agent when you need to refactor large or complex codebases, extract components into modules, improve code organization, or when files have grown unwieldy and need restructuring. This agent should be used proactively when you notice code complexity issues, mixed responsibilities, or when planning architectural…

clchinkc/document-mcp · 217 tokens

debug-analyzer

Use this agent when you need to debug issues, analyze error logs, trace problems across modules, or investigate system failures. Examples: Context: User encounters a failing test and needs to understand the root cause. user: 'The integration tests are failing with MCP connection errors. Can you help me debug this?'…

clchinkc/document-mcp · 225 tokens

opus-researcher

Use this agent when you need comprehensive research, analysis, and synthesis of complex topics. This agent excels at gathering information from multiple sources, identifying patterns and connections, evaluating evidence quality, and producing well-structured research outputs with proper citations and methodology.…

clchinkc/document-mcp · 239 tokens