your-docs-mcp: Agent for Claude Code

.claude/agents/doc-editor.md

doc-editor is an agent for Claude Code from esola-thomas/your-docs-mcp. It costs 33 tokens per session (2,606 once invoked), scanned C, original, MIT.

An expert documentation editor for improving existing technical documents while preserving their intent, structure, and consistency.

In plain words
What is it for?
Use it to revise, correct, format, and maintain documentation, including checking related standards and updating relevant frontmatter.
Why use it?
It reduces unclear writing, formatting problems, and changes that conflict with a project's documentation standards.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

This is esola-thomas/your-docs-mcp's own configuration. It tells Claude Code how to work on your-docs-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything your-docs-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to esola-thomas/your-docs-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/esola-thomas/your-docs-mcp/main/.claude/agents/doc-editor.md
Clone the repo
git clone --depth 1 https://github.com/esola-thomas/your-docs-mcp

Made for: Claude Code.

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

agentmods badge for doc-editor

README.md
[![agentmods](https://agentmods.dev/badge/agents/esola-thomas/your-docs-mcp/doc-editor/github.svg)](https://agentmods.dev/agents/esola-thomas/your-docs-mcp/doc-editor)
Your own site
<a href="https://agentmods.dev/agents/esola-thomas/your-docs-mcp/doc-editor"><img src="https://agentmods.dev/badge/agents/esola-thomas/your-docs-mcp/doc-editor/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.

agentmods 80×15 button for doc-editor

Your own site · 80×15
<a href="https://agentmods.dev/agents/esola-thomas/your-docs-mcp/doc-editor"><img src="https://agentmods.dev/badge/agents/esola-thomas/your-docs-mcp/doc-editor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,606 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00033 $0.02606
Opus 5.5 $0.00013 $0.01042
Sonnet 5.5 $0.00007 $0.00521
Haiku 4.5 $0.00003 $0.00261

Measured 2mo ago against content hash 7a4e88ce5090, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

doc-editor scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

​``` code without language ​``` # After (correct): ​```python code with language specified ​``` ``` #### 3. Link Corrections **Internal Links:** - Use relative paths: `./file.md` or `../parent/file.md` - Include `.md` ex
.claude/agents/doc-editor.md · 506 lines

How it starts

The opening of the file, as written. The whole thing — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior technical editor specializing in improving and maintaining documentation. You excel at enhancing clarity, fixing formatting issues, updating content, and ensuring consistency across documentation while preserving the original intent and maintaining project standards.

Core Responsibilities

When invoked to edit documentation:

  1. Read the target documentation file completely
  2. Review .claude/DOCUMENTATION_STANDARDS.md for current standards
  3. Analyze what needs to be changed and why
  4. Preserve existing structure and intent unless specifically changing it
  5. Make precise, targeted edits using the Edit tool
  6. Verify changes maintain formatting and standards compliance
  7. Update frontmatter fields if needed (e.g., updated date)

Documentation Editing Checklist

Pre-Edit Analysis

  • Read complete current version
  • Understand purpose and scope of requested changes
  • Identify all sections requiring modification
  • Check for impact on related documentation
  • Note current frontmatter values
  • Review existing formatting and style

Edit Types and Approaches

1. Content Updates

Adding New Content:

  • Maintain existing structure and flow
  • Match writing style and voice
  • Add to appropriate section
  • Update table of contents if needed
  • Ensure proper markdown formatting

Modifying Existing Content:

  • Preserve original intent unless changing it
  • Maintain consistent terminology
  • Keep code examples up to date
  • Update related sections for consistency
  • Verify technical accuracy

Removing Content:

  • Ensure no orphaned references
  • Update table of contents
  • Check for dependent content
  • Verify links still work
2. Formatting Corrections

YAML Frontmatter:

# Common fixes:
- Ensure proper quoting: title: "Title with: colon"
- Valid YAML syntax: proper indentation
- Complete required fields: title, category, tags, order
- Update 'updated' field when making changes

Read the full file on GitHub · 506 lines

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. 2mo ago First seen · 506 lines · 33 tokens per session scan C 7a4e88ce5090

Subscribe to this mod's changes

doc-editor is an agent published in the GitHub repository esola-thomas/your-docs-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 2,606 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

doc-editor compared with agents from other repositories

doc-editor next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
doc-editoresola-thomas/your-docs-mcpAgent03mo agoMITC33Claude Code
quarto-criticbrycewang-stanford/Auto-Empirical-Research-SkillsAgent4.9k4d agononeA38Claude Code
openwriter-enrichment-miniontravsteward/openwriterAgent365d agoMITA19Claude Code
report-generatordaemon-blockint-tech/GrondAgent21mo agoMITA195Claude Code
chronology-builderfedec65/bettercallclaudeAgent461mo agoAGPL-3.0A103Claude Code
flow-documenterMacroMan5/AutomationHelper_pluginsAgent31y agoMITA368Claude Code
ops-documentacaoasv-digital/agents-funcionariosAgent26mo agononeA0Claude Code