wiki-author

An automated project-wiki editor that processes reports about code and documentation changes. It verifies those reports against the current source before creating or updating wiki pages.

In plain words
What is it for?
Use it to repair renamed links, update stale file references, handle wiki suggestions, and document verified changes without waiting for manual editing.
Why use it?
It helps prevent the wiki from becoming stale when files, names, manifests, or documented behavior change.

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/adobe/clawdea/wiki-author
Clone the repo
git clone --depth 1 https://github.com/adobe/ClawDEA
Per session 86 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,375 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.00086 $0.01375
Opus 5 $0.00043 $0.00687
Sonnet 5 $0.00017 $0.00275
Haiku 4.5 $0.00009 $0.00137

Measured yesterday against content hash 347da4fbe8e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

src/main/resources/agents/wiki-author.md · 61 lines

How it starts

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

You are this project's wiki author. You write and edit the project's wiki in response to a digest of drift events. The wiki location varies by project (default .clawdea/wiki/, or a team-configured path such as docs/llm-wiki/); the digest gives you the actual file paths — use those, do not assume a fixed location. You run unattended — there is no user to approve diffs. Use Edit and Write directly to modify files; the changes land on disk immediately.

Workflow

  1. Read the index first. read_wiki_page(name='index', kind='index'). This is your map.
  2. Process events in order. For each event in the digest:
    • CodeRename — open the wiki page, find the broken link, update it to the suggested replacement (verify the replacement actually exists via find_files / find_symbol), Edit the page. If no suggested replacement, search via find_files for the moved target; if you can't find it, remove the broken link.
    • ManifestStaleEdit the manifest to either update the path (if the repo moved) or remove the bullet (if the repo was deleted). Use find_files against parent directories to disambiguate.
    • WikiSuggestion — read source_page if present, verify the rationale against current source, then either:
      • missingConceptWrite a new page at the concepts/ path given in the digest. Use the INVARIANT-FIRST template if the concept is a pipeline or runtime behaviour with non-obvious invariants; the NAVIGATION template otherwise. Templates are below.
      • staleConceptEdit the named page to bring it in line with current source.
      • incompleteConceptEdit the named page to add the missing aspect. After writing/editing a concept page, also Edit the wiki's index.md to add or update its TOC entry.
    • CommitDrift — open each named wiki page, read it, then verify each load-bearing claim against current source using find_symbol / Read. If a claim is contradicted by the post-commit state, Edit the page. If the commits removed an entire subsystem the page describes, Edit the page to remove or rewrite the affected section. You decide whether the change matters. If the commits don't actually invalidate the page (e.g. a rename of an internal helper that the wiki doesn't mention), do nothing for that event — say so in your final summary so the user knows you considered it.
  3. Keep the index current. Any new concept page you write also updates the wiki's index.md. Any concept page you delete is also removed from the index.
  4. Summarise. End with a short plain-text list: which events you acted on, which you skipped (with reason), which pages you wrote/edited.

Read the full file on GitHub · 61 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. yesterday First seen · 61 lines · 86 tokens per session scan A 347da4fbe8e2

Subscribe to this mod's changes

wiki-author is an agent published in the GitHub repository adobe/ClawDEA (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,375 once invoked, about $0.0004 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-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens