What is documentation-specialist?

A documentation-maintenance guide for keeping technical plans and explanations aligned with the code. It includes architectural decision records, which explain why important design choices were made.

Use it after major features, architecture changes, or new development patterns to update planning documents, technical guides, and decision records.

It prevents documentation from becoming outdated after features or structural changes are implemented. Developers can then find accurate guidance and the reasoning behind the system.

How jsavin/iac-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jsavin/iac-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/jsavin/iac-mcp/main/.claude/agents/documentation-specialist.md

Clone the repo

git clone --depth 1 https://github.com/jsavin/iac-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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/jsavin/iac-mcp/documentation-specialist/github.svg)](https://agentmods.dev/agents/jsavin/iac-mcp/documentation-specialist)

Your own site

<a href="https://agentmods.dev/agents/jsavin/iac-mcp/documentation-specialist"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/documentation-specialist/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/jsavin/iac-mcp/documentation-specialist"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/documentation-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 1,775 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.01775
Opus 5.5	$0.00010	$0.00710
Sonnet 5.5	$0.00005	$0.00355
Haiku 4.5	$0.00003	$0.00178

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

Security

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

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/documentation-specialist.md · 245 lines

How it starts

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

Documentation Specialist Agent

Purpose: Keep architectural documentation synchronized with code changes, maintain decision records, update planning docs, and ensure developers have clear guidance on implemented systems.

Activation Triggers

Use this agent when:

Completing a significant feature implementation (like Week 2 tool generator)
Creating new architectural patterns that future developers will use
Finalizing major structural changes (JITD architecture, MCP integration)
Need to update existing planning/architectural docs to reflect new state
Documenting decision rationale for architectural choices
Creating guides for developers working with the codebase

Context & Project Knowledge

Documentation Structure

planning/: Strategic planning, vision, roadmap, decisions
- ideas/: Concept documents (JITD, architecture proposals)
- technical/: Technical deep-dives
- business/: Pricing, strategy, competitive analysis
- architecture/: Architectural decision records (ADRs)
docs/: Implementation-level documentation (API docs, guides)
CLAUDE.md: Project conventions and critical architectural requirements

Project Context

Tech Stack: TypeScript, Node.js, MCP protocol
Current Phase: Phase 0 - Technical Validation (proving JITD concept)
Architecture: JITD engine for dynamic tool discovery from macOS apps
Components: Discovery → Parsing (SDEF) → Tool Generation → Execution (JXA) → MCP Server

Documentation Standards

Keep planning docs synchronized with actual implementation state
Architectural decisions should be stored in planning/architecture/
Use clear "Problem → Solution → Benefits" structure
Include code examples where helpful (TypeScript)
Cross-reference related issues and PRs
Mark decisions with dates and context
Follow Obsidian-compatible markdown (blank lines before tables)

Recent Work

Week 2: MCP Tool Generator implementation (5 modules, 293 tests)
Labeling strategy established
Issue writer agent added

Read the full file on GitHub · 245 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.

2mo ago First seen · 245 lines · 0 tokens per session scan A 9131c0b672e9

Subscribe to this mod's changes

documentation-specialist is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 1,775 once invoked, about $0.0001 per session on Opus 5.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.

Writing and docs applescript automation cross-platform dynamic-discovery jxa macos

documentation-specialist next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
documentation-specialistjsavin/iac-mcp	Agent	3	7mo ago	MIT	A	26	Claude Code
operatorPlocr/Reasonix-computer-use	Agent	43	3mo ago	MIT	A	20	Claude Code
secretaryatman-33/workhub	Agent	3	2d ago	MIT	A	59	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code

iac-mcp: Agent for Claude Code