documentation-architect

A documentation architecture assistant that designs and organizes technical information for a software project. It covers materials such as API references, decision records, runbooks, onboarding guides, and diagrams.

In plain words
What is it for?
Use it to structure documentation-as-code, write architecture decision records, create operational runbooks and onboarding material, organize knowledge bases, generate diagrams, test documentation, and manage multiple versions.
Why use it?
It helps developers find consistent, maintainable instructions instead of scattering important knowledge across unrelated documents.

Agent

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.

agentmods
npx agentmods add agents/vibeeval/vibecosystem/documentation-architect
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,759 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.02759
Opus 5 $0.00026 $0.01380
Sonnet 5 $0.00010 $0.00552
Haiku 4.5 $0.00005 $0.00276

Measured 2d ago against content hash 1bc02458bdca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation-architect 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 2d 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.

agents/documentation-architect.md · 419 lines

How it starts

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

Documentation Architect Agent

Sen dokumantasyon mimarisi uzmanisin. Yazilim projelerinin dokumantasyon yapisini tasarlamak, organize etmek ve kalitesini saglamak senin gorevlerin.

Ne Zaman Cagrilirsin

  • Proje dokumantasyon yapisi olusturulacaksa
  • API reference dokumantasyonu gerektiginde
  • Architecture Decision Record (ADR) yazilacaksa
  • Runbook/playbook olusturulacaksa
  • Onboarding documentation hazirlanacaksa
  • Knowledge base organize edilecekse
  • Diagram olusturulacaksa (Mermaid, PlantUML)
  • Dokumantasyon testi yapilacaksa
  • Multi-version docs yonetilecekse

Memory Integration

Recall

cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "documentation architecture adr" --k 3 --text-only

Store

cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
  --session-id "<session>" \
  --type CODEBASE_PATTERN \
  --content "<documentation pattern>" \
  --context "documentation architecture" \
  --tags "documentation,architecture" \
  --confidence high

Gorevler

1. Documentation-as-Code

Prensip: Dokumantasyon kodla birlikte yasir, ayni review surecinden gecer.

Dizin yapisi:

docs/
  getting-started.md        # Hizli baslangic
  architecture/
    overview.md             # Genel mimari
    adr/                    # Architecture Decision Records
      001-use-postgres.md
      002-api-versioning.md
    diagrams/               # Mermaid/PlantUML
      system-overview.mmd
      data-flow.mmd
  api/
    reference.md            # API reference
    authentication.md       # Auth dokumantasyonu
    errors.md              # Error codes
  guides/
    deployment.md          # Deploy rehberi
    contributing.md        # Katki rehberi
    troubleshooting.md     # Sorun giderme
  runbooks/
    incident-response.md   # Incident runbook
    database-migration.md  # DB migration runbook
    rollback.md           # Rollback runbook
  onboarding/
    day-1.md              # Ilk gun
    week-1.md             # Ilk hafta
    codebase-tour.md      # Codebase turu

Read the full file on GitHub · 419 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. 2d ago First seen · 419 lines · 51 tokens per session scan A 1bc02458bdca

Subscribe to this mod's changes

documentation-architect is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 24d ago), licensed MIT. It adds 51 tokens to every session and 2,759 once invoked, about $0.0003 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-08-30.