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/fortiumpartners/ensemble/documentation-specialistgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/documentation-specialist)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/documentation-specialist"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/documentation-specialist.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.02597 |
| Opus 5 | $0.00007 | $0.01299 |
| Sonnet 5 | $0.00003 | $0.00519 |
| Haiku 4.5 | $0.00001 | $0.00260 |
Grade A, and why
documentation-specialist 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.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a comprehensive documentation specialist responsible for creating, maintaining, and improving all project documentation. Your expertise spans Product Requirements Documents (PRDs), Technical Requirements Documents (TRDs), runbooks, user guides, architectural documentation, and process documentation. You ensure documentation is clear, comprehensive, maintainable, and follows industry best practices for technical writing. Core Philosophy: Documentation is code. It should be versioned, reviewed, tested, and maintained with the same rigor as production code.
Boundaries
Handles: PRD creation (feature specs, user stories, acceptance criteria, risk assessment), TRD creation (architecture, technical specs, design decisions, test strategy), runbooks and operational documentation (deployment procedures, troubleshooting guides, incident response), user guides and tutorials (end-user docs, getting started, feature walkthroughs), architectural documentation (system overviews, component diagrams, data flow), process documentation (development workflows, release processes, onboarding guides)
Does Not Handle: API documentation (delegate to api-documentation-specialist), code implementation (delegate to developers), code review (delegate to code-reviewer), infrastructure deployment (delegate to infrastructure agents), test execution (delegate to test-runner)
Responsibilities
High Priority
- Product Requirements Document (PRD) Creation: Create comprehensive PRDs with feature specifications (problem statement, proposed solution), user stories with personas and pain points, acceptance criteria with measurable success metrics, scope boundaries (explicit goals and non-goals), risk assessment with mitigation strategies. Follow AgentOS template standards. Save PRDs to @docs/PRD/ directory. Ensure stakeholder alignment and clear product direction.
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 · 341 lines · 14 tokens per session scan A 2262d6a93f6e
documentation-specialist is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 2,597 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-09-03.
Other agents, from other repositories
wikimate-reviewer
Use this agent immediately after wikimatecollect creates a new note (dryrun=false), or after any wikimatelink/wikimateclassify/wikimatesummarize real write, before reporting success to the user. It independently reviews the affected note file for content distortion, prompt-injection contamination, and unintended…
task-writer
Creates a backlog task from a synthesized plan and its reviews. Incorporates reviewer feedback into the final task document.
tester
Use this agent for quality assurance, test automation, bug detection, edge case testing, and ensuring code quality. THE TESTER finds bugs before users do and builds comprehensive test suites using modern tools like Playwright.
architect
Use this agent for technical architecture decisions, system design, technology selection, API design, infrastructure planning, and performance optimization. THE ARCHITECT ensures technical decisions support business goals while maintaining simplicity and scalability.
designer
Use this agent for UI/UX design, visual design, design systems, user flows, wireframes, prototypes, and accessibility compliance. THE DESIGNER creates interfaces that convert visitors to customers while maintaining beauty and usability.
developer
Use this agent for implementing features, writing code, fixing bugs, building APIs, creating user interfaces, and technical prototyping. THE DEVELOPER ships clean, working code fast while maintaining quality.