Borrowing it
Nothing to install: this file belongs to synaptic-ai-consulting/AAMAD. 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/synaptic-ai-consulting/AAMAD/main/.cursor/skills/sync-docs/SKILL.mdgit clone --depth 1 https://github.com/synaptic-ai-consulting/AAMADWrote 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/synaptic-ai-consulting/aamad/sync-docs)<a href="https://agentmods.dev/skills/synaptic-ai-consulting/aamad/sync-docs"><img src="https://agentmods.dev/badge/skills/synaptic-ai-consulting/aamad/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/synaptic-ai-consulting/aamad/sync-docs"><img src="https://agentmods.dev/badge/skills/synaptic-ai-consulting/aamad/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.00075 | $0.00772 |
| Opus 5.5 | $0.00030 | $0.00309 |
| Sonnet 5.5 | $0.00015 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync docs
Closing step for the persona that just changed code. The review is automatic. The write waits for the operator.
Invocation: *sync-docs, or the end of any change set of application source, runtime config, env examples, or deploy/CI config.
Owned by the persona the operator invoked. Only @project.mgr, @frontend.eng, @backend.eng, @integration.eng, and @devops.eng run this skill. @product-mgr, @system.arch, @ux.designer, @qa.eng, and @security.eng do not.
Read reference.md for the allowlist, proposal shape, and loop guard.
When to run
Run this skill once after a change set of:
- application source
- runtime or adapter config that the generated app loads
.env.examplekeys or comments- deploy or CI config
Do not run it because you just edited this persona's own epic markdown while implementing (for example filling in backend.md). Do not run it again because of edits this skill just made.
If this turn only wrote documentation, stop.
What you may change
Descriptive docs only, and only sentences the change made false. The allowlist is in reference.md.
Define and Review stay authoritative. Do not edit project-context/1.define/** or project-context/0.review/**. If the code contradicts the PRD, SAD, SFS, or a Review artifact, list that as spec drift and do not patch the spec. The operator chooses whether to revert the code or hand the spec change to @system.arch or @product-mgr.
Do not invent requirements. Do not expand a sentence into a new section. Do not create a README.md that does not already exist.
Procedure
- Read the files you just changed and every allowlisted doc that exists.
- Compare stated facts (endpoint, port, env var name, start command, stack, path) to the code.
- If nothing descriptive is stale, append one Audit line on this persona's own artifact (
Doc sync: no updates; timestamp, persona id,sync-docs) and stop. Do not ask a question. - If something is stale, present one proposal and stop. Do not write the docs in the same turn.
- After the operator answers, write only the approved items. Append an Audit block (timestamp, persona id,
sync-docs) on each file touched. Record rejected items under Open Questions on this persona's own artifact.
What ships with it
1 file 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 · 70 lines · 75 tokens per session scan A 953856af1abf
sync-docs is a skill published in the GitHub repository synaptic-ai-consulting/AAMAD (88 stars, last pushed 4d ago), licensed Apache-2.0. It adds 75 tokens to every session and 772 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-10-25.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…