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/dds-solutions/ai-tadpole-os/documentation-writergit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/documentation-writer)<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="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.1 | $0.00029 | $0.01340 |
| Opus 5 | $0.00015 | $0.00670 |
| Sonnet 5 | $0.00006 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 5d 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`. How it starts
The opening of the file, as written. The whole thing — 80 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
/conceptsor/glossarydirectory 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.
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.
- 5d ago First seen · 80 lines · 29 tokens per session scan D 3dfe3a29a11d
documentation-writer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,340 once invoked, about $0.0001 per session on Opus 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.
Other agents, from other repositories
typescript-architect
Architecture specialist for claude-code-history-viewer's typescript code (react). Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the typescript architecture — not for crude surface patches.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
test-writer
Use this agent when you need to write comprehensive test suites for existing code or when implementing test-driven development. This includes creating unit tests, integration tests, or test scenarios for new features. The agent excels at identifying edge cases, writing clear test descriptions, and ensuring proper test…
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…