A skill for updating an existing OpenWiki-format project wiki so it matches recent source-code changes. OpenWiki is a structured documentation format for repositories.

Use it to compare the current code with the previous update, identify affected documentation, and edit the relevant wiki pages. The wiki must already exist.

It prevents the wiki from becoming outdated after code changes and preserves the format required by the OpenWiki tools.

update — Skill for Claude Code by jatinmayekar

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add jatinmayekar/openwiki-for-claude-code

Claude Code

/plugin install openwiki

Made for: Claude Code.

Or install openwiki, the plugin that ships this one along with the rest of its 4 skills.

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/skills/jatinmayekar/openwiki-for-claude-code/update/github.svg)](https://agentmods.dev/skills/jatinmayekar/openwiki-for-claude-code/update)

Your own site

<a href="https://agentmods.dev/skills/jatinmayekar/openwiki-for-claude-code/update"><img src="https://agentmods.dev/badge/skills/jatinmayekar/openwiki-for-claude-code/update/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/skills/jatinmayekar/openwiki-for-claude-code/update"><img src="https://agentmods.dev/badge/skills/jatinmayekar/openwiki-for-claude-code/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 818 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.00054	$0.00818
Opus 5.5	$0.00022	$0.00327
Sonnet 5.5	$0.00011	$0.00164
Haiku 4.5	$0.00005	$0.00082

Measured 2mo ago against content hash 30f80e6fec20, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update 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 2mo 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/openwiki/skills/update/SKILL.md · 50 lines

How it starts

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

OpenWiki: update

Refresh the existing openwiki/ wiki so it reflects recent source changes — doing the work yourself with your own tools (Read, Grep, Glob, Edit, Bash for git). Do not call the openwiki CLI and do not require any API key.

First, read the format spec: ${CLAUDE_PLUGIN_ROOT}/reference/openwiki-format.md (layout, metadata, exact AGENTS.md/CLAUDE.md block, principles, security). Updates must stay compatible with the OpenWiki CLI.

Steps

Locate the wiki. If openwiki/ doesn't exist yet, tell the user to run /openwiki:generate first and stop.
Read prior metadata. Read openwiki/.last-update.json. Prefer its gitHead as the baseline; fall back to updatedAt if no gitHead.
Find what changed. Use git: git diff <gitHead>..HEAD --stat, then targeted diffs on the high-signal changed files. Also git status/git diff for uncommitted changes touching docs or important source. If shell/git is unavailable, infer from file timestamps and source inspection.
Build a docs-impact plan (do not write it to disk unless helpful): for each meaningful source change → which wiki page is affected → what edit is needed → why. If a page can't be tied to a relevant change, do not touch it.
Edit surgically.
- Only edit pages made inaccurate/incomplete/misleading by the changes.
- Prefer replacing a stale sentence over adding paragraphs. Preserve accurate structure/wording.
- No formatting-only edits. Don't reformat tables, normalize blank lines, reorder lists, or polish wording unless you're already changing that content for accuracy.
- Don't refresh Source Map / git-evidence / generic "things to watch" sections unless they are materially wrong now.
- Soft diff budget: if fewer than ~5 source files changed, edit at most 1–2 pages. Avoid touching quickstart.md unless top-level product behavior, setup, or navigation changed. If you think >3 pages need edits, reconsider carefully first.
Check the reference section. Ensure the top-level AGENTS.md/CLAUDE.md OpenWiki section is present and current (see the format spec). Refresh only if missing or semantically stale.
No-op is allowed. If nothing relevant changed and the wiki is already accurate, make no edits at all — leave every file, including openwiki/.last-update.json, untouched — and tell the user the wiki is already current. (Upstream only records metadata when content actually changes.)
Write metadata (only if you changed wiki content). Update openwiki/.last-update.json with command: "update", updatedAt from date -u +%Y-%m-%dT%H:%M:%S.000Z (run it — don't guess), the current git rev-parse HEAD, and your model.
Report which pages changed and why, or that the wiki was already current.

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

2mo ago First seen · 50 lines · 54 tokens per session scan A 30f80e6fec20

Subscribe to this mod's changes

update is a skill published in the GitHub repository jatinmayekar/openwiki-for-claude-code (19 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 818 once invoked, about $0.0002 per session on Opus 5.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

update next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
updatejatinmayekar/openwiki-for-claude-code	Skill	19	4mo ago	MIT	A	54	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code