update-docs

A process for checking project documentation against the current code and updating anything that is inaccurate or outdated.

In plain words
What is it for?
Use it to update setup guides, API documentation, architecture notes, plans, configuration examples, and other project documents after code changes.
Why use it?
It helps prevent documentation from drifting away from how the software actually works. It first maps the available documentation, then checks relevant areas and applies fixes.

Skill for Claude CodeCodex

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 skills/iofold/ainative-claude-plugins/update-docs
Any agent
npx skills add iofold/ainative-claude-plugins --skill update-docs
Clone the repo
git clone --depth 1 https://github.com/iofold/ainative-claude-plugins

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00057 $0.01333
Opus 5 $0.00028 $0.00666
Sonnet 5 $0.00011 $0.00267
Haiku 4.5 $0.00006 $0.00133

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

Security

Grade B, and why

update-docs scanned grade B with 1 finding 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.

Recursive force deletemediumDestructive command

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

rm -rf .tmp/docs-audit

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

project-planning/skills/update-docs/SKILL.md · 226 lines

How it starts

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

Update Documentation

Systematically verify and update project documentation using parallel explore agents in explore-exploit turns.

Overview

This skill uses an adaptive approach:

  1. Discovery - Map what documentation exists in the project
  2. Planning - Determine which areas can be explored in parallel
  3. Exploration - Dispatch agents based on discovered structure
  4. Exploitation - Apply fixes and updates

Arguments

If $ARGUMENTS provided, use as a focus hint but still discover the actual structure first.

Phase 1: Discovery (Single Agent)

Launch ONE discovery agent first to map the documentation landscape:

subagent_type: "Explore"
description: "Map documentation structure"
prompt: |
  Map all documentation in this project.

  Tasks:
  1. Find all documentation files and directories:
     - Glob for **/*.md, **/docs/**, **/*.rst, **/*.txt
     - Check for swagger/openapi specs
     - Find .env.example, config examples
     - Look for diagrams (*.mmd, *.puml, *.drawio)

  2. Categorize what exists:
     - README files (root and nested)
     - API documentation
     - Setup/installation guides
     - Architecture/design docs
     - Implementation plans/specs
     - Inline code documentation patterns
     - Configuration documentation
     - Changelogs/release notes

  3. Note project characteristics:
     - Approximate size (file count)
     - Primary language/framework
     - Documentation style/format used

  4. Identify documentation gaps:
     - Directories with no README
     - Undocumented public APIs
     - Missing setup instructions

  Write findings to .tmp/docs-audit/discovery.md

  Format:
  ## Documentation Map

  ### Project Profile
  - Size: [small/medium/large]
  - Language: [primary language]
  - Framework: [if applicable]

  ### Documentation Found
  | Category | Files | Status |
  |----------|-------|--------|
  | README | [list] | [exists/missing] |
  | API Docs | [list] | [exists/missing] |
  ...

  ### Recommended Parallel Exploration Areas
  Based on what exists, these areas can be explored in parallel:
  1. [area]: [files to check]
  2. [area]: [files to check]
  ...

  ### Gaps Identified
  - [gap description]

Read the full file on GitHub · 226 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 226 lines · 57 tokens per session scan B af00ff3a6316

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository iofold/ainative-claude-plugins (3 stars, last pushed 14d ago), licensed MIT. It adds 57 tokens to every session and 1,333 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens