What is plan-docs-sync?

A review plan that compares documentation with what the code actually does. It covers items such as READMEs, setup instructions, API references, environment examples, command help, and architecture notes.

Use it to check whether project docs, examples, and onboarding steps still match the current codebase.

Out-of-date documentation can give developers false instructions, point to APIs that no longer exist, or make onboarding fail. It identifies the differences and plans corrections without rewriting the documents yet.

plan-docs-sync — Skill for Claude Code by kensaurus/cursor-kenji

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 kensaurus/cursor-kenji --skill plan-docs-sync

Clone the repo

git clone --depth 1 https://github.com/kensaurus/cursor-kenji

Made for: Claude Code.

Or install cursor-kenji, the plugin that ships this one along with the rest of its 132 skills, 63 commands, 6 agents, 1 hook, 3 MCP servers.

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/kensaurus/cursor-kenji/plan-docs-sync/github.svg)](https://agentmods.dev/skills/kensaurus/cursor-kenji/plan-docs-sync)

Your own site

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

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

When invoked 1,240 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.00081	$0.01240
Opus 5.5	$0.00032	$0.00496
Sonnet 5.5	$0.00016	$0.00248
Haiku 4.5	$0.00008	$0.00124

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

Security

Grade B, and why

plan-docs-sync 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 1mo 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.

Harvests environment variablesmediumData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

**Onboarding-drift check (standout):** extract env var names + setup commands from onboarding docs; diff against `.env.example` keys and `package.json` scripts; run CLI `--help` where safe and compare.

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

skills/plan-docs-sync/SKILL.md · 141 lines

How it starts

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

Docs Drift Audit + Sync Plan

Degree of freedom: MIXED — inventory globs are exact; drift judgment is high. Stay plan-only. No rewrites until approved.

Role: Senior engineer + technical writer.

Task: Audit all documentation against what the code actually does, find every drift, plan corrections. README, CONTRIBUTING, setup/onboarding, API docs, JSDoc/docstrings, architecture notes, .env.example, CLI --help, changelogs. Audit & plan only.

This skill vs neighbors

Skill	Does
plan-docs-sync (this)	Plan doc corrections from code truth
`docs-writer`	Write/improve docs (execution)
`workflow-housekeep`	README refresh as part of housekeeping
`plan-stub-checker`	Stubs/dead UI — often surfaces phantom docs

Loop position: run last in the six-skill plan loop. See docs/PLAN-LOOPS.md.

How to reason (every plan item)

Propose — correction that makes the doc match code truth
Risk — onboard fail, phantom API, or invented behavior if left stale
Keep-working — claims already backed by path:line
Phase — factual drift first; wording last (do not execute)

Worked example

Propose: drop STRIPE_WEBHOOK_SECRET from the README setup list (absent from .env.example and code); document POST /v1/webhooks/stripe which exists undocumented. Risk: onboarding fails on a phantom env var; integrators miss a live endpoint. Keep-working: CONTRIBUTING install steps match package.json scripts. Phase: first sync slice — factual drift only.

⛔ Preservation Contract [LOW freedom — run exactly]

Read references/preservation-contract.md. Acknowledge in output #1.

Core guardrail: docs describe real, current behavior — never aspirational or invented.

References

File	Contents
`references/drift-taxonomy.md`	Types, detection passes, guardrails
`references/output-templates.md`	Burndown, phased sync plan

Read the full file on GitHub · 141 lines

Files

What ships with it

3 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.

1mo ago First seen · 141 lines · 81 tokens per session scan B 64165f1cb087

Subscribe to this mod's changes

plan-docs-sync is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 81 tokens to every session and 1,240 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Project management Writing and docs agent-skills ai-agent claude cursor cursor-ai cursor-ide

pre-mortem-facilitator

Facilitate a pre-mortem session using Shreyas Doshi's Tigers/Paper Tigers/Elephants framework. Use when the user is planning a launch, starting a critical project, preparing for a major initiative, or wants to proactively identify risks before something goes wrong.

luisabwk/kraken · 65 tokens

plan-docs-sync