A release-documentation checker for Scraps, a software project with a documentation website, README files, and plugin guides. It compares what a released version changed with what those documents still say.

Use it after publishing a release or when checking whether documentation matches a version. It reviews release notes and changed files, then proposes and applies the updates the user selects.

It finds release changes that were shipped without matching documentation updates, including outdated behavior, missing feature pages, and stale screenshots. It avoids proposing edits that the release already documented.

How boykush/scraps configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to boykush/scraps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/boykush/scraps/main/.agents/skills/doc-update/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/boykush/scraps

Made for: Claude Code, Codex.

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/boykush/scraps/doc-update/github.svg)](https://agentmods.dev/skills/boykush/scraps/doc-update)

Your own site

<a href="https://agentmods.dev/skills/boykush/scraps/doc-update"><img src="https://agentmods.dev/badge/skills/boykush/scraps/doc-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/boykush/scraps/doc-update"><img src="https://agentmods.dev/badge/skills/boykush/scraps/doc-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 813 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.00085	$0.00813
Opus 5.5	$0.00034	$0.00325
Sonnet 5.5	$0.00017	$0.00163
Haiku 4.5	$0.00009	$0.00081

Measured 23d ago against content hash 3799d7b8ff78, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-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 23d 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.

.agents/skills/doc-update/SKILL.md · 52 lines

How it starts

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

Doc update

Feature PRs normally update their docs in the same change. This skill looks for what slipped through anyway:

behaviour the release changed that the docs still describe the old way
pages where a new feature should appear but doesn't
screenshots that no longer match

Takes a version such as 3.1.0. Without one, use the latest release (gh release view --json tagName).

1. Read what shipped

gh release view v<version> --json body lists the PRs by section, with breaking changes first.
Keep what users would notice: breaking changes, features, fixes, and performance changes. Skip maintenance.
For each PR you keep, gh pr view <N> --json files --jq '.files[].path' shows which docs it already updated. Don't propose those changes again.

2. Find where each change belongs

Surface	Where	Holds
Docs site	`docs/`	A Scraps wiki laid out by Diátaxis in `Tutorial/`, `How-to/`, `Reference/` and `Explanation/`. `docs/README.md` is the index page
README	`README.md`	Quick start, how Scraps works, AI integration, screenshots
MCP tool reference	`plugins/mcp-server/README.md`	Parameters and response shape of every MCP tool
Plugin overviews	`plugins/*/README.md`	What each plugin bundles
Screenshots	`assets/`	Images the README embeds

Pages move between releases, so list the tree (git ls-files docs README.md plugins assets) rather than assuming paths. To find everything that mentions a changed command, flag, config key or term, run git grep -n "<term>" -- docs README.md plugins. An exact match catches stale mentions that fuzzy search misses.

Usual homes for a change:

A command, flag or --json field: docs/Reference/CLI Overview.md. If agents use it, also docs/How-to/Integrate with AI Assistants.md.
A config key: docs/Reference/Configuration.md
A lint rule: docs/Reference/Lint Rules.md
An MCP tool: plugins/mcp-server/README.md
A change in what CI needs, such as checkout depth or action inputs: docs/How-to/Deploy to GitHub Pages.md
A new major version: every boykush/scraps@v<major> reference

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

23d ago First seen · 52 lines · 85 tokens per session scan A 3799d7b8ff78

Subscribe to this mod's changes

doc-update is a skill published in the GitHub repository boykush/scraps (45 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 813 once invoked, about $0.0003 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-09-25.

Rust Writing and docs cli knowledge-management markdown static-site-generator wiki

llmwiki

Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.

atomicstrata/llm-wiki-compiler · 66 tokens

processing-markdown

Processes Markdown files using mq, a jq-like query language for Markdown. Use when the user mentions Markdown processing, content extraction, document transformation, or mq queries.

harehare/mq · 36 tokens

web-scraping

Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…

harehare/mq · 89 tokens

scraps: Skill for Claude Code