Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.cursor/skills/review-and-sync-docs/SKILL.mdgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/review-and-sync-docs)<a href="https://agentmods.dev/skills/lsampaioweb/ai-instructions/review-and-sync-docs"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/review-and-sync-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.
<a href="https://agentmods.dev/skills/lsampaioweb/ai-instructions/review-and-sync-docs"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/review-and-sync-docs.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00375 |
| Opus 5 | $0.00026 | $0.00187 |
| Sonnet 5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
review-and-sync-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 10d 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.
What it actually says
Markdown Documentation Sync Engine
- Obey
AGENTS.md(project root). - Present a read-only update plan before applying edits.
1. Scope & Analysis
- Resolve the target scope from the user-provided input.
- Fallback Scan: If scope is omitted, inspect uncommitted workspace changes (
git status,git diff) first, then evaluate recent commits. - Correlate code and configuration deltas with impacted Markdown targets.
2. Resolution Rules
- Execution Target: Update Markdown only when code or configuration changes alter documented behavior or setup.
- README Boundary: Update
*.mdonly when the mapped change affects onboarding, execution, or architecture. - Style Match: Match existing formatting and voice.
- Correction Protocol — Content: Repair stale instructions, outdated keys, and deprecated paths.
- Correction Protocol — References: Resolve broken links and replace obsolete examples.
3. Safety Guards
- Forbidden: Do not invent features, parameters, properties, or runtime behavior absent from the codebase.
- Uncertainty Gate: If a documentation update cannot be verified with available code context, stop and ask focused questions before editing.
4. Review Plan Layout
Present a read-only update plan before applying edits:
Synced Files:
- path/to/doc1.md
Structural Updates:
- <what changed and why>
Verification Points:
- <uncertainties requiring confirmation>
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.
- 10d ago First seen · 48 lines · 53 tokens per session scan A 614f75f1a535
review-and-sync-docs is a skill published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 375 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…