A workflow for updating project documentation after a feature change, refactor, or removal. It finds related documents, edits them, and adds a new one only when needed.

It helps maintain feature guides, architecture notes, and agent rules, while reporting which files changed.

It keeps documentation from describing old behaviour or missing newly changed parts of the project.

update-docs — Skill for Cursor by BOXELS/cursor-rules

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.

Any agent

npx skills add BOXELS/cursor-rules --skill update-docs

Clone the repo

git clone --depth 1 https://github.com/BOXELS/cursor-rules

Made for: Cursor.

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/boxels/cursor-rules/update-docs/github.svg)](https://agentmods.dev/skills/boxels/cursor-rules/update-docs)

Your own site

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

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

When invoked 659 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.00090	$0.00659
Opus 5	$0.00045	$0.00329
Sonnet 5	$0.00018	$0.00132
Haiku 4.5	$0.00009	$0.00066

Measured yesterday against content hash c7a282b2308a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-16, from the pricing page.

Security

Grade A, and why

update-docs 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 yesterday.

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.

.cursor/skills/update-docs/SKILL.md · 54 lines

How it starts

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

Update Docs

Run this whenever the user asks to update documentation, or after a change that other agents will need to know about. Do all five steps before reporting back. Do not ask the user which files to touch — find them.

Doc folder, naming convention, and what belongs in a doc are defined in .cursor/rules/documentation.mdc. Read it first if you haven't this session.

Workflow

- [ ] 1. Find related docs
- [ ] 2. Update existing docs in place
- [ ] 3. Create a new doc only if none covers the area
- [ ] 4. Cross-reference from .cursor/rules/
- [ ] 5. Report every file touched

1. Find related docs

Search the doc folder for files related to the work just performed. Derive search terms from feature names, table names, routes, and component names touched. If several docs might be relevant, read their headers and update every one that mentions the affected area.

2. Update existing docs in place

Edit, don't append. Remove references to deleted patterns. Do not leave incomplete or contradictory information. Prefer editing an existing doc over creating a duplicate.

3. Create a new doc only when none exists

Only if no existing file covers the area. Follow the naming convention in documentation.mdc. A new feature doc includes: one-sentence purpose, files/routes/tables touched, how it works, critical constraints (things agents must NOT do), and links to related docs. Document only what was actually implemented — never invent behavior.

4. Cross-reference from `.cursor/rules/`

If the change affects patterns or conventions other agents need:

Cross-cutting concern → global-rules.mdc.
Domain-specific → the matching rule file (tech.mdc, design.mdc, security.mdc, models.mdc, structure.mdc), or a new focused .mdc file.
Add a one-line "see docs/FOO.md" pointer from the rule when a longer reference exists.
New rule files must use the .mdc extension with description, globs, and alwaysApply frontmatter. Scope with globs when the rule only matters for certain file types.

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

yesterday First seen · 54 lines · 90 tokens per session scan A c7a282b2308a

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository BOXELS/cursor-rules (6 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 659 once invoked, about $0.0005 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-09-15.

Writing and docs

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens