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/movahedan/monobun/documentation-syncnpx skills add movahedan/monobun --skill documentation-syncgit clone --depth 1 https://github.com/movahedan/monobunWrote 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/movahedan/monobun/documentation-sync)<a href="https://agentmods.dev/skills/movahedan/monobun/documentation-sync"><img src="https://agentmods.dev/badge/skills/movahedan/monobun/documentation-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 | $0.00047 | $0.02380 |
| Opus 5 | $0.00023 | $0.01190 |
| Sonnet 5 | $0.00009 | $0.00476 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
documentation-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 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation sync
When to use
- Scripts, workspaces, Docker, CI, or public commands changed and docs may drift.
- Editing or reviewing
README.md,AGENTS.md,docs/**, or.cursor/rules/*.mdc. - User asks which docs to update or to refresh onboarding and command references.
Position in the initiative pipeline
Run after builder-workflow completes a plan phase (checkup PASS). Run before git-pr-workflow.
Full order: initiative-workflow.
| Do | Do not |
|---|---|
| Sync docs once code/config for the phase is stable | Edit docs during builder scout/implement/checkup |
| Use the plan’s Documentation before PR path list | Drive-by doc edits outside that list |
Re-run targeted rg for stale paths/commands |
Replace the plan’s verify gate |
Prerequisite message from user: “Phase N build complete. documentation-sync per plan doc list.”
Content ownership (do not duplicate)
| Topic | Owner | documentation-sync may… |
|---|---|---|
| Plan → build → docs → PR | initiative-workflow | Link one line only |
| Subagents, model tiers | builder-workflow/orchestration.md | Not edit unless on plan doc list |
| Commit / branch / PR | git-pr-workflow | Not describe steps |
TS strict / noExplicitAny |
tools/typescript/base.json, biome.json |
Reference paths in rules/AGENTS if renamed |
| Command tables | docs/CHEATSHEET.md | Sync when root package.json scripts change |
| Quick setup | README.md | Single bootstrap section; link CHEATSHEET for commands |
| Compose / layout / troubleshooting | AGENTS.md | Workspaces table, ports column, nested guides |
| This phase’s doc files | Plan Documentation before PR | Edit only listed paths |
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 · 258 lines · 47 tokens per session scan A b59ae9cf0159
documentation-sync is a skill published in the GitHub repository movahedan/monobun (18 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,380 once invoked, about $0.0002 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…