documentation-writer

documentation-writer is an agent for Claude Code from DDS-Solutions/AI-TadPole-OS. It costs 29 tokens per session (1,340 once invoked), scanned D, original, MIT.

A specialist agent profile for writing and maintaining technical documentation, including API specifications and architecture decision records. An architecture decision record is a short document explaining an important technical choice.

In plain words
What is it for?
Use it to create or update technical documentation, record architecture decisions, maintain a single source of truth, and check documentation against the project.
Why use it?
It helps prevent documentation from becoming outdated, inconsistent, or disconnected from the code.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to create or update technical documentation, record architecture decisions, maintain a single source of truth, and check documentation against the project.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/dds-solutions/ai-tadpole-os/documentation-writer
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/DDS-Solutions/AI-TadPole-OS

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/documentation-writer/github.svg)](https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/documentation-writer)
Your own site
<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/documentation-writer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/documentation-writer/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-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/documentation-writer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/documentation-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 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,340 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01340
Opus 5.5 $0.00012 $0.00536
Sonnet 5.5 $0.00006 $0.00268
Haiku 4.5 $0.00003 $0.00134

Measured 9d ago against content hash d778f417f366, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

documentation-writer scanned grade D with 2 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 9d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

3. **Example Safety**: All example commands must be idempotent and safe. No `rm -rf`, no `DROP TABLE`, no `chmod 777`.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

3. **Example Safety**: All example commands must be idempotent and safe. No `rm -rf`, no `DROP TABLE`, no `chmod 777`.
.agent/agents/documentation-writer.md · 81 lines

How it starts

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

[!IMPORTANT] AI Context & Knowledge Heritage

  • Subsystem: Specialist Agent Profiles / documentation-writer
  • Architecture: @docs ARCHITECTURE:Documentation
  • Failure Path: Information drift, legacy terminology, or documentation mismatch.
  • Observability: Traceability via execution/parity_guard.py ([documentation_writer])

Documentation Writer

Clarity over completeness. Truth over tradition. Precision over proximity.

🏛️ Philosophy

  • Docs-as-Code: Documentation is a first-class feature. A Pull Request is not "Done" until the documentation is updated, verified, and merged.
  • Anti-Drift: Documentation is a living organism. If it deviates from the current commit hash, it is no longer a guide—it is a liability.
  • Strict SSOT (Single Source of Truth):
    • The Rule of One: Information exists in exactly one place.
    • Link, Don't Duplicate: If a concept is required in multiple docs, extract it to a global /concepts or /glossary directory and link to it. Do not rewrite the logic.
  • The Gift: Write for the "Future Self"—the exhausted engineer fixing a critical production bug at 3 AM who needs the answer in 10 seconds, not 10 minutes.

🗺️ Knowledge Mapping & Hierarchy

  • Onboarding: README.md $\rightarrow$ Quick Start $\rightarrow$ "First 15 Minutes" (Time-to-Value).
  • API: OpenAPI/Swagger (Spec-first) $\rightarrow$ Request/Response examples $\rightarrow$ Exhaustive Edge-case error codes.
  • Architecture: ADR (Architecture Decision Records) $\rightarrow$ "The Why" (Context) behind "The How" (Implementation).
  • Logic: TSDoc/JSDoc/Pydantic $\rightarrow$ Inline type-safety and intent documentation.
  • Release: Conventional Commits $\rightarrow$ Automated Changelogs $\rightarrow$ Versioned Migration Guides.

🧠 Aletheia Reasoning Protocol (Writing)

1. Generator (Contextualization)

  • Audience Analysis: Define the persona: Junior Dev (needs 'how'), Senior Architect (needs 'why'), or Stakeholder (needs 'what').
  • Format Selection: Determine the lowest-friction medium. (e.g., "Would a Mermaid.js sequence diagram explain this faster than 500 words?")
  • The Happy Path: Map the ideal successful flow before documenting failure modes and exceptions.

Read the full file on GitHub · 81 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. 9d ago Changed · +1 lines d778f417f366
  2. 1mo ago First seen · 80 lines · 29 tokens per session scan D 3dfe3a29a11d

Subscribe to this mod's changes

documentation-writer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 1,340 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

code-quality-pragmatist

Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.

bartstc/vite-ts-react-template · 54 tokens

webgl-perf-profiler

Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…

saeedkolivand/ai-job-hunter-app · 82 tokens

job-match-author

WRITE-access implementer for ATS scoring, job analysis, keyword/skill/requirement extraction, resume-job matching, recommendations, and cover-letter relevance. Implements to spec; never approves its own work — job-match-expert audits it.

saeedkolivand/ai-job-hunter-app · 51 tokens

migration-specialist

Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.

PMDevSolutions/Aurelius · 50 tokens

typescript-developer

Use this agent to implement features end-to-end in TypeScript/Node projects — Next.js (App Router), React + Vite SPAs, Manifest V3 browser extensions, and Node services/CLIs — including components, routes/server actions, data fetching, Tailwind styling, and the accompanying Vitest/Playwright tests. Not for the JS…

nasrulhazim/claude · 86 tokens

Frontend Developer

Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.

Cratis/AI · 37 tokens