agentmods.dev

update

update is a skill for Claude Code from jatinmayekar/openwiki-for-claude-code. It costs 54 tokens per session (818 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
It prevents the wiki from becoming outdated after code changes and preserves the format required by the OpenWiki tools.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the openwiki plugin — 4 skills shipped together

not rated 18 2mo ago A scan 54 tokens original MIT
View the source file jatinmayekar/openwiki-for-claude-code
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.

agentmods badge for update

README.md
[![agentmods](https://agentmods.dev/badge/skills/jatinmayekar/openwiki-for-claude-code/update.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.svg" alt="Measured on agentmods" 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. 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.1 $0.00054 $0.00818
Opus 5 $0.00027 $0.00409
Sonnet 5 $0.00011 $0.00164
Haiku 4.5 $0.00005 $0.00082

Measured 6d ago against content hash 30f80e6fec20, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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

  1. Locate the wiki. If openwiki/ doesn't exist yet, tell the user to run /openwiki:generate first and stop.
  2. Read prior metadata. Read openwiki/.last-update.json. Prefer its gitHead as the baseline; fall back to updatedAt if no gitHead.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.)
  8. 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.
  9. 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.

  1. 6d 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 (18 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 818 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.

Writing and docs
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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens