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/cmdr-chara/codex-toolkit/documentation-synchronizernpx skills add cmdr-chara/codex-toolkit --skill documentation-synchronizergit clone --depth 1 https://github.com/cmdr-chara/codex-toolkitWhat 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.00073 | $0.01635 |
| Opus 5 | $0.00036 | $0.00817 |
| Sonnet 5 | $0.00015 | $0.00327 |
| Haiku 4.5 | $0.00007 | $0.00163 |
Grade A, and why
documentation-synchronizer 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Synchronizer
Treat documentation as a distributed contract with users, developers, operators, and integrators.
Trigger boundary
Use this skill for:
- identifying docs affected by an implementation or migration diff;
- synchronizing user guides, API references, configuration, examples, architecture, runbooks, and release notes;
- auditing stale commands, options, screenshots, generated docs, or cross-links;
- verifying a documentation-only change against current code and public contracts.
Do not trigger for:
- deciding what the product should do;
- visual brand/campaign copy unrelated to repository behavior;
- a code change with no externally or operationally meaningful documentation surface;
- generating API docs by editing generated output instead of its source.
Required inputs
Obtain:
- changed files/diff and final intended behavior;
- repository documentation map and audience/release context;
- authoritative sources for APIs, schemas, config, CLI, environment, and defaults;
- supported versions and migration/deprecation policy;
- documentation tooling, generators, link/check commands, and localization policy;
- known generated, translated, versioned, or externally hosted documentation boundaries.
If behavior is ambiguous, stop and return the exact implementation question. Do not resolve ambiguity through prose.
Safety baseline
- Inspect worktree state and preserve unrelated edits.
- Do not rewrite all docs to normalize style; update only impacted surfaces and necessary consistency links.
- Do not edit generated docs directly unless the repository explicitly treats them as source.
- Never copy secrets, production identifiers, private URLs, or personal data into examples.
- Mark destructive examples clearly and provide safe prerequisites; do not invent executable commands.
- Keep version-specific instructions scoped and dated where they can become stale.
Workflow
1. Extract the contract delta
Summarize changes under applicable categories:
What ships with it
4 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 · 193 lines · 73 tokens per session scan A b85fe20fffd3
documentation-synchronizer is a skill published in the GitHub repository cmdr-chara/codex-toolkit (2 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 1,635 once invoked, about $0.0004 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
boss-advanced
Advanced Boss orchestration patterns — Agent Teams leadership, 6-section delegation template, Skill vs Agent conflict resolution, Guardian pattern, and AI-slop detection.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
agent-orchestrator-v2
Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and…
agent-orchestration-multi-agent-optimize-v2
Multi-Agent Optimization Toolkit workflow skill. Use this skill when the user needs Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability and the operator should preserve the upstream workflow…
briefing-vault
Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.