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/kevinzai/commander/ccc-doc-syncnpx skills add KevinZai/commander --skill ccc-doc-syncgit clone --depth 1 https://github.com/KevinZai/commanderWhat 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.00028 | $0.00910 |
| Opus 5 | $0.00014 | $0.00455 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
ccc-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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-doc-sync — Doc Count Synchronizer
Keeps every count reference (plugin_skills, specialist_agents, hook_handlers) and version string in sync across the entire project. One source of truth — never manually edit numbers in docs again.
What it does
Reads two canonical sources:
commander/contract.json—plugin_skills,specialist_agents,hook_handlerspackage.json—version
Then applies surgical regex replacements across 20+ doc files, updating every occurrence of stale counts. Idempotent — running twice produces the same output.
How it works
- Load values from
contract.json+package.json - Read
patterns.json— declarative per-file replacement rules - For each file: apply all patterns, compare before/after
--check: report drift, exit 1 if any file is stale (CI gate)--apply: write changes, exit 0
The pattern engine uses ${plugin_skills}, ${specialist_agents}, ${hook_handlers}, ${version} template vars. Adding support for a new file is a JSON edit in patterns.json — no code change.
Files covered
| Category | Files |
|---|---|
| Root docs | README.md, BIBLE.md, CHEATSHEET.md, SKILLS-INDEX.md, CLAUDE.md |
| Plugin manifest | commander/cowork-plugin/.claude-plugin/plugin.json, CONNECTORS.md |
| Mintlify docs | introduction.mdx, install.mdx, agents.mdx, skills.mdx, free-vs-pro.mdx, install-recovery.mdx |
| Site components | site/components/hero.tsx, site/components/skills-showcase.tsx |
| Video scenes | scene-hero.jsx, scene-agents.jsx, scene-compare.jsx, scene-hooks.jsx, scene-install.jsx |
Usage
# Dry-run — show what would change, exit 1 if drift detected
node commander/cowork-plugin/skills/ccc-doc-sync/sync.js --check
# Apply changes
node commander/cowork-plugin/skills/ccc-doc-sync/sync.js --apply
# Via npm scripts
npm run docs:sync:check # CI gate (--check)
npm run docs:sync # Apply all changes
When to run
- After bumping
contract.jsonplugin_skills count (new skill added) - After bumping
contract.jsonspecialist_agents count (new agent added) - After bumping
contract.jsonhook_handlers count (new handler added) - After running
npm version(updates package.json version) docs:sync:checkruns automatically inprepublishOnly
What ships with it
2 files 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.
- 2d ago First seen · 106 lines · 28 tokens per session scan A f731620e317e
ccc-doc-sync is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 910 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.