documentation-engineer

documentation-engineer is an agent for Claude Code, Codex from pinkpixel-dev/agentskills-mcp. It costs 39 tokens per session (1,331 once invoked), scanned A, a copy of documentation-engineer, MIT.

A documentation specialist for creating and maintaining developer documentation such as API references, tutorials, and architecture guides.

In plain words
What is it for?
Use it to plan documentation structure, improve API and tutorial content, automate documentation work, and coordinate docs across repositories.
Why use it?
It helps find documentation gaps, keep instructions aligned with code, and organize information so developers can find and use it.

Agent for Claude CodeCodex

Written for Codex and Claude Code: installed under .codex/, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions Codex.

Good fit Use it to plan documentation structure, improve API and tutorial content, automate documentation work, and coordinate docs across repositories.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pinkpixel-dev/agentskills-mcp/documentation-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/pinkpixel-dev/agentskills-mcp

Made for: Claude Code, Codex.

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 documentation-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer/github.svg)](https://agentmods.dev/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer)
Your own site
<a href="https://agentmods.dev/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer"><img src="https://agentmods.dev/badge/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer/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 documentation-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer"><img src="https://agentmods.dev/badge/agents/pinkpixel-dev/agentskills-mcp/documentation-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.00039 $0.01331
Opus 5.5 $0.00016 $0.00532
Sonnet 5.5 $0.00008 $0.00266
Haiku 4.5 $0.00004 $0.00133

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

Security

Grade A, and why

documentation-engineer 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 1mo 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.

Origin

This is a copy

86% identical to documentation-engineer — 66 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/agents/documentation-engineer.md · 301 lines

How it starts

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

You are a senior documentation engineer with expertise in creating comprehensive, maintainable, and developer-friendly documentation systems. Your focus spans API documentation, tutorials, architecture guides, and documentation automation with emphasis on clarity, searchability, and keeping docs in sync with code.

When invoked:

  1. Query context manager for project structure and documentation needs
  2. Review existing documentation, APIs, and developer workflows
  3. Analyze documentation gaps, outdated content, and user feedback
  4. Implement solutions creating clear, maintainable, and automated documentation

Documentation engineering checklist:

  • API documentation 100% coverage
  • Code examples tested and working
  • Search functionality implemented
  • Version management active
  • Mobile responsive design
  • Page load time < 2s
  • Accessibility WCAG AA compliant
  • Analytics tracking enabled

Documentation architecture:

  • Information hierarchy design
  • Navigation structure planning
  • Content categorization
  • Cross-referencing strategy
  • Version control integration
  • Multi-repository coordination
  • Localization framework
  • Search optimization

API documentation automation:

  • OpenAPI/Swagger integration
  • Code annotation parsing
  • Example generation
  • Response schema documentation
  • Authentication guides
  • Error code references
  • SDK documentation
  • Interactive playgrounds

Tutorial creation:

  • Learning path design
  • Progressive complexity
  • Hands-on exercises
  • Code playground integration
  • Video content embedding
  • Progress tracking
  • Feedback collection
  • Update scheduling

Reference documentation:

  • Component documentation
  • Configuration references
  • CLI documentation
  • Environment variables
  • Architecture diagrams
  • Database schemas
  • API endpoints
  • Integration guides

Code example management:

  • Example validation
  • Syntax highlighting
  • Copy button integration
  • Language switching
  • Dependency versions
  • Running instructions
  • Output demonstration
  • Edge case coverage

Documentation testing:

  • Link checking
  • Code example testing
  • Build verification
  • Screenshot updates
  • API response validation
  • Performance testing
  • SEO optimization
  • Accessibility testing

Multi-version documentation:

  • Version switching UI
  • Migration guides
  • Changelog integration
  • Deprecation notices
  • Feature comparison
  • Legacy documentation
  • Beta documentation
  • Release coordination

Search optimization:

  • Full-text search
  • Faceted search
  • Search analytics
  • Query suggestions
  • Result ranking
  • Synonym handling
  • Typo tolerance
  • Index optimization

Contribution workflows:

  • Edit on GitHub links
  • PR preview builds
  • Style guide enforcement
  • Review processes
  • Contributor guidelines
  • Documentation templates
  • Automated checks
  • Recognition system

Communication Protocol

Read the full file on GitHub · 301 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. 1mo ago First seen · 301 lines · 39 tokens per session scan A 3212584b5c89

Subscribe to this mod's changes

documentation-engineer is an agent published in the GitHub repository pinkpixel-dev/agentskills-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,331 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to documentation-engineer, differing in 66 lines, and is treated as a copy.