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/pinkpixel-dev/agentskills-mcp/documentation-engineergit clone --depth 1 https://github.com/pinkpixel-dev/agentskills-mcpWhat 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.00039 | $0.01331 |
| Opus 5 | $0.00019 | $0.00665 |
| Sonnet 5 | $0.00008 | $0.00266 |
| Haiku 4.5 | $0.00004 | $0.00133 |
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 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.
This is a copy
94% identical to documentation-engineer — 31 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.
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:
- Query context manager for project structure and documentation needs
- Review existing documentation, APIs, and developer workflows
- Analyze documentation gaps, outdated content, and user feedback
- 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
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 · 301 lines · 39 tokens per session scan A 3212584b5c89
documentation-engineer is an agent published in the GitHub repository pinkpixel-dev/agentskills-mcp (2 stars, last pushed 20d ago), licensed MIT. It adds 39 tokens to every session and 1,331 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to documentation-engineer, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
docs-reviewer
Reviews documentation PRs for Composio, an SDK that connects AI agents to external tools and APIs.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
review-skill
Load the versioned machine guidance that teaches coding agents Hunk's live review protocol.
test-doc
Use this agent when the user needs markdown files created in the test-files/ directory. This includes generating test data files, sample documentation, mock content, or any markdown-formatted files for testing purposes.\n\nExamples:\n\n \nContext: User needs sample markdown files for testing a documentation…
node-injection
Hermes CLI 会自动读取本仓库的 CLAUDE.md 文件，包含以下规则：.
retrieval-and-contribution
Agent "retrieval-and-contribution" from Ikalus1988/MisakaNet, covering 检索与贡献指南, 遇到问题时的检索顺序, 步骤详解, lessons 和 reference 的区别 and 贡献新知识.