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.00078 | $0.00529 |
| Opus 5.5 | $0.00031 | $0.00212 |
| Sonnet 5.5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
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 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.
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
Arguments
- Optional scope, folder path, or feature-area filter.
- Omit the filter to sync from uncommitted changes, then recent commits.
1. Define the Scope
- Resolve the target scope from the user-provided arguments when present.
- Fallback Scan: If scope is omitted, inspect
git status, unstaged changes withgit diff, staged changes withgit diff --cached, and the contents of untracked files listed bygit status. Then evaluate commits made after the latest commit whose subject starts withdocs:; if no such baseline exists, evaluate the latest 10 commits. - Correlate code and configuration deltas with impacted Markdown targets.
2. Resolution Rules
- What to update: Update
*.mdonly when code or configuration changes alter documented onboarding, execution, or architecture behavior. - Match the existing style: Follow the current formatting, heading style, and list conventions.
- Content corrections: Repair stale instructions, outdated keys, and deprecated paths.
- Reference corrections: Resolve broken links and replace obsolete examples.
3. Safety Guards
- Execution Boundary: Apply Markdown edits only after the read-only plan is presented and the user explicitly confirms.
- Fabrication Guard: Never 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
Use this exact markdown schema:
Scope
- Target:
- Mode: <read-only | apply-after-confirmation>
Result
- Summary:
Evidence
- Synced files: <none | path1; path2>
- Structural updates: <none | item1; item2>
- Verification points: <none | item1; item2>
Next Action
- <single minimal next step or
none>
Verdict
- READY | NEEDS FIXES | BLOCKED
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 Changed 87cc071e6999
- 1mo ago Changed · +11 lines · +25 tokens per session 87db15fe2713
- 2mo 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 5d ago), licensed MIT. It adds 78 tokens to every session and 529 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-08-31.
review-and-sync-docs compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| review-and-sync-docslsampaioweb/ai-instructions | Skill | 1 | 5d ago | MIT | A | 78 | Cursor |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |