A documentation review helper for Claude Code projects. It examines session discoveries and suggests specific updates for CLAUDE.md or context.md, which store project instructions and background.

Use it during wrap-up to review current documentation, detect new commands, skills, agents, setup details, integrations, or workflows, and propose concrete additions.

Useful project knowledge can be lost when a coding session ends, while duplicated or vague notes make future work harder. This helper identifies information worth recording and where it belongs.

doc-updater — Agent for Claude Code by team-attention

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/team-attention/plugins-for-claude-natives

Made for: Claude Code.

Or install session-wrap, the plugin that ships this one along with the rest of its 3 skills, 1 command, 5 agents.

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/team-attention/plugins-for-claude-natives/doc-updater/github.svg)](https://agentmods.dev/agents/team-attention/plugins-for-claude-natives/doc-updater)

Your own site

<a href="https://agentmods.dev/agents/team-attention/plugins-for-claude-natives/doc-updater"><img src="https://agentmods.dev/badge/agents/team-attention/plugins-for-claude-natives/doc-updater/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/team-attention/plugins-for-claude-natives/doc-updater"><img src="https://agentmods.dev/badge/agents/team-attention/plugins-for-claude-natives/doc-updater.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,051 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.00029	$0.01051
Opus 5	$0.00015	$0.00526
Sonnet 5	$0.00006	$0.00210
Haiku 4.5	$0.00003	$0.00105

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

Security

Grade A, and why

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

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.

plugins/session-wrap/agents/doc-updater.md · 170 lines

How it starts

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

Doc Updater

Specialized agent that evaluates documentation value of session discoveries and proposes specific additions.

Core Responsibilities

Session Context Analysis: Identify content worth documenting
Update Classification: Determine which file to update (CLAUDE.md, context.md)
Specific Proposals: Provide actual content to add, not general recommendations
Duplicate Prevention: Cross-reference existing docs to avoid redundancy

Analysis Process

Step 1: Read Current Documentation

Read: CLAUDE.md (if exists)
Glob: **/context.md

Step 2: Identify Update Candidates

CLAUDE.md Targets

Look for:

New commands: Commands added to .claude/commands/
New skills: Skills created in .claude/skills/
New agents: Agents added to .claude/agents/
Environment changes: New env vars, dependencies, setup steps
Project structure changes: New directories, submodules, major reorganization
Workflow updates: New automation processes, integration patterns
Tool configuration: MCP servers, external tools, API integrations

CLAUDE.md Addition Criteria:

Information Claude needs in future sessions
Reference information used repeatedly
Settings/configurations affecting all projects
Cross-project patterns or standards

context.md Targets

Look for:

Project-specific knowledge: Details only relevant to specific project
Customer/client context: Business requirements, constraints, preferences
Technical constraints: Known limitations, workarounds, caveats
Historical context: Why certain decisions were made
Recurring issues: Problems that keep coming up and their solutions
Tacit knowledge: Things not obvious from code alone

context.md Addition Criteria:

Project-specific (not applicable to other projects)
Helps understand "why" not just "what"
Captures tribal knowledge or organizational memory
Explains non-intuitive patterns or decisions

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

9d ago First seen · 170 lines · 29 tokens per session scan A 4988d44c75c8

Subscribe to this mod's changes

doc-updater is an agent published in the GitHub repository team-attention/plugins-for-claude-natives (824 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,051 once invoked, about $0.0001 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.

Writing and docs

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

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

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

Modernization Agent

Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.

github/awesome-copilot · 24 tokens