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 skills add omergocmen/vibe-coder-kit --skill documentation-syncgit clone --depth 1 https://github.com/omergocmen/vibe-coder-kitWrote 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/omergocmen/vibe-coder-kit/documentation-sync)<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/documentation-sync"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/documentation-sync/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/omergocmen/vibe-coder-kit/documentation-sync"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/documentation-sync.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.00046 | $0.01169 |
| Opus 5.5 | $0.00018 | $0.00468 |
| Sonnet 5.5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Sync Skill
When to Trigger
Run after:
- A public API endpoint is added, changed, or removed
- A CLI command or flag is modified
- A new environment variable or config key is introduced
- A major component or module is refactored
- A new npm/pip/etc. package is added or removed from dependencies
- Any
README.mdreference becomes inaccurate
Step-by-Step Process
1. Identify What Changed
Review the git diff of the work just completed:
git diff main --name-only # Files changed vs main
git diff HEAD~1 --name-only # Files changed in last commit
Categorize changes:
- API changes → affects
docs/api/, OpenAPI/Swagger specs,README.md - Config changes → affects
.env.example,docs/configuration.md - Dependency changes → affects
README.md(setup section),docs/getting-started.md - Architecture changes → affects
docs/architecture.md, diagrams - New features → affects
docs/features/, changelogs
2. Audit Existing Docs
For each affected category, check whether corresponding docs exist:
docs/
api/ ← REST/GraphQL endpoint docs
architecture.md ← System design, component diagram
configuration.md ← All env vars and config options
getting-started.md ← Local setup guide
features/ ← Per-feature descriptions
CHANGELOG.md ← Version history
README.md ← Project overview + quickstart
For each doc file that touches the changed area, read it and flag stale sections.
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 First seen · 169 lines · 46 tokens per session scan A e9d063cd98a8
documentation-sync is a skill published in the GitHub repository omergocmen/vibe-coder-kit (95 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,169 once invoked, about $0.0002 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-30.
Other skills, from other repositories
tdd
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/ /, verify APIs via web search, then implement in tiny test-verified steps.
electron-desktop-builder
Converts a web app (Express, React, Vite, Next.js) into an Electron desktop app. Use when starting a new Electron project from an existing web app, when setting up electron-builder for the first time, when creating main.ts/preload.ts boilerplate, when generating icon assets, or when configuring NSIS installers.…
ai-skill-auditor
A universal, dependency-free Node.js tool to statically audit AI Skills and local agents for malicious patterns.
c4-architecture-c4-architecture
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
embedding-strategies
Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.