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.
npx skills add kensaurus/cursor-kenji --skill plan-docs-syncgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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.
[](https://agentmods.dev/skills/kensaurus/cursor-kenji/plan-docs-sync)<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="Measured on agentmods" height="20"></a>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 | $0.00041 | $0.00620 |
| Sonnet 5 | $0.00016 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
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 4d 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.
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_SECRETfrom the README setup list (absent from.env.exampleand code); documentPOST /v1/webhooks/stripewhich exists undocumented. Risk: onboarding fails on a phantom env var; integrators miss a live endpoint. Keep-working: CONTRIBUTING install steps matchpackage.jsonscripts. 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 |
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.
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.
- 4d ago First seen · 141 lines · 81 tokens per session scan B 64165f1cb087
plan-docs-sync is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 81 tokens to every session and 1,240 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
help-center-article-generator
Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders, troubleshooting sections, and related article links. Batch mode generates multiple articles from a ticket export. Pure reasoning…
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…