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 agentmods add skills/tykisgod/quick-question/doc-syncnpx skills add tykisgod/quick-question --skill doc-syncgit clone --depth 1 https://github.com/tykisgod/quick-questionWhat 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 | $0.00066 | $0.01709 |
| Opus 5 | $0.00033 | $0.00855 |
| Sonnet 5 | $0.00013 | $0.00342 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
doc-sync 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Local, on-demand documentation synchronization. This is the third trigger mode for doc maintenance, complementing the event-driven layer (pre-commit warn) and the scheduled layer (periodic report): the human runs it when they know they've changed something doc-affecting, to pull drifted docs back in line with the code — but the human keeps the landing authority.
Relationship to qq:doc-drift: doc-drift is report-only (it outputs a P0/P1/P2 attention list). doc-sync is the reconcile loop — it calls doc-drift (and the project's drift detectors) as its detection stage, then adds the two stages doc-drift lacks: draft the fixes and land what the human approves.
Arguments: $ARGUMENTS
- No arguments: full sweep of the project's living docs
--since <ref>: only docs affected by code changed since<ref>(windowed reconcile)--scope <design|memory|seams|rules>: restrict to one class of living doc--all: include archived/historical docs (default excludesDocs/archive/and old review artifacts)
Principle (do not violate)
Detectors are read-only; doc-sync is the sole writer; the human is the sole lander. Reference drift (a dead anchor) is auto-drafted; semantic/process drift is only flagged for the human to decide. Graphs say "what is wired now"; the seam registry says "what should be wired / what breaks if missing" — neither overwrites the other.
Execution Flow
1. Discover the project's drift tooling (project-aware)
Probe for these and use whatever exists — degrade gracefully when absent (a generic project just gets doc-drift + git-diff reasoning):
| If present | Use it for |
|---|---|
Tools/blast_radius.py |
"changed files → affected docs + code-side ripple" (diff [base] / who <token>) |
Tools/check_doc_drift.py |
symbol-anchor drift in docs (LINEREF / missing file / missing GUID / 0-hit symbol) |
Tools/check_memory.py |
memory consistency + staleness (audit); re-stamp via stamp <date> <files> |
Tools/check_seams.py |
.claude/seams.yml anchor drift |
.claude/seams.yml |
cross-cutting seam registry (fan-out points) |
Tools/asset_graph.py / Tools/event_graph.py |
Unity asset / event-bus blast-radius |
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.
- 2d ago First seen · 79 lines · 66 tokens per session scan A dc94bbafda7d
doc-sync is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 8d ago), licensed MIT. It adds 66 tokens to every session and 1,709 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.