What is documentation-sync?

A set of instructions for keeping code, specifications, architecture notes, agent guides, and project memories synchronized. It applies to documentation and policy files as well as source-code changes.

Use it when changing source code, documentation, architecture, agent rules, README files, memories, or CI policy. It defines which documents to update and which repository checks to run.

It reduces the risk that instructions or documentation describe behavior different from the implementation. It also requires checking links, mirrored guides, and repository rules after relevant edits.

documentation-sync — Skill by SioYooo

Install

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.

agentmods

npx agentmods add skills/sioyooo/repogrammar/documentation-sync

Any agent

npx skills add SioYooo/RepoGrammar --skill documentation-sync

Clone the repo

git clone --depth 1 https://github.com/SioYooo/RepoGrammar

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 629 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.00629
Opus 5	$0.00015	$0.00315
Sonnet 5	$0.00006	$0.00126
Haiku 4.5	$0.00003	$0.00063

Measured today against content hash a10ace1e528a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

.agents/skills/documentation-sync/SKILL.md · 79 lines

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.

Purpose

Keep implementation, canonical documentation, skills, memories, and mirrored agent guides synchronized.

Trigger conditions

Use when touching src/, docs/, .agents/skills/, .agents/memories/, AGENTS.md, CLAUDE.md, README, CHANGELOG, or CI policy.

Required reading

docs/README.md
docs/development/documentation-policy.md
docs/architecture/module-map.md
.agents/memories/README.md

Preconditions

Identify the canonical source for the changed topic.
Check whether the change makes a memory stale.

Step-by-step procedure

Update the canonical document first.
Update dependent references only where needed.
Keep requirements duplicated in multiple places byte- or meaning-consistent.
If either root guide changes, run guide sync immediately.
Validate relative links by inspection for every changed Markdown file.
Run repository guard.

Required verification

cargo run --quiet --bin repo-guard -- check
cmp -s AGENTS.md CLAUDE.md

Documentation updates

Follow this minimum matrix:

Code range	Required document
`src/rust/core/model/`	`docs/specifications/domain-model.md`
`src/rust/core/mining/`	`docs/specifications/indexing-pipeline.md`
`src/rust/core/policy/`	domain model, product spec, or related ADR
`src/rust/ports/`	dependency rules and related specification
`src/rust/adapters/parsing/`	indexing pipeline and dependency rules
`src/rust/adapters/languages/`	indexing pipeline and roadmap
`src/rust/adapters/semantic_workers/`	semantic worker specification and ADR-0004
`src/rust/adapters/frameworks/`	indexing pipeline and roadmap
`src/rust/adapters/persistence/`	storage specification and related ADR
`src/rust/application/`	architecture overview, module map, and relevant specification
`src/rust/interfaces/cli/`	README and CLI specification
`src/rust/interfaces/mcp/`	`docs/specifications/mcp-api.md`
`src/rust/bin/repo_guard.rs`	`docs/development/repository-guard.md`
`src/workers/`	semantic worker specification
`src/protocol/`	semantic worker specification

Read the full file on GitHub · 79 lines

Changes

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.

today First seen · 79 lines · 31 tokens per session scan A a10ace1e528a

Subscribe to this mod's changes

documentation-sync is a skill published in the GitHub repository SioYooo/RepoGrammar (0 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 629 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-31.

DevOps and cloud Memory and context Writing and docs code-analysis coding-agents developer-tools local-first mcp rust

od-contribute

One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…

nexu-io/open-design · 104 tokens

clinical-case-report

Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…

nexu-io/open-design · 73 tokens

critique

Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks…

nexu-io/open-design · 107 tokens

github-dashboard

GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.

nexu-io/open-design · 55 tokens

dating-web

A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social…

nexu-io/open-design · 87 tokens

dcf-valuation

Discounted cash flow valuation and intrinsic value analysis for public companies. Use when the brief asks for DCF, fair value, intrinsic value, price target, undervalued or overvalued analysis, or "what is this company worth?".