doc-sync

doc-sync is a skill for Claude Code, Codex from monkey1wizard/Golem-Agents-Legion. It costs 46 tokens per session (1,521 once invoked), scanned A, original, MIT.

A documentation-maintenance workflow that maps code changes to affected documentation in an NDJSON structure map. NDJSON is a text format with one JSON object per line.

In plain words
What is it for?
It helps inspect Git changes, update the structure map, validate its records, and render documentation views when needed.
Why use it?
It helps detect documentation that may be out of date after code changes while preserving map entries that were not rechecked.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps inspect Git changes, update the structure map, validate its records, and render documentation views when needed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monkey1wizard/golem-agents-legion/doc-sync
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.

Any agent
npx skills add monkey1wizard/Golem-Agents-Legion --skill doc-sync
Clone the repo
git clone --depth 1 https://github.com/monkey1wizard/Golem-Agents-Legion

Made for: Claude Code, Codex.

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

agentmods badge for doc-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/doc-sync/github.svg)](https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/doc-sync)
Your own site
<a href="https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/doc-sync"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/doc-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.

agentmods 80×15 button for doc-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/doc-sync"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/doc-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01521
Opus 5.5 $0.00018 $0.00608
Sonnet 5.5 $0.00009 $0.00304
Haiku 4.5 $0.00005 $0.00152

Measured 28d ago against content hash c473f872f9c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 28d 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.

plugins/gal-core/skills/doc-sync/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Doc Sync Workflow

Use this skill to keep documentation structure aligned with code changes through the tracked NDJSON map in docs/structure/.

What This Skill Owns

  • Read and update docs/structure/structure-map.ndjson one JSON record per line.
  • Validate records against docs/structure/structure-map.schema.json when a validator is available.
  • Map file-level code changes to code-axis and doc-axis nodes.
  • Keep untouched nodes unchanged; update only nodes re-verified in the current run.
  • Render human-facing projections on demand without creating tracked projection files.

Core Inputs

  • docs/structure/structure-map.schema.json
  • docs/structure/structure-map.ndjson
  • templates/structure-map.template.ndjson
  • changed-file set from git diff
  • affected docs under docs/ and README.md

Operating Rules

1. Drift Detection Baseline

  • Always start from native git diff plus direct file reads.
  • Treat graphify and codebase-memory-mcp as advisory-only enhancement lanes.
  • If an advisory lane is unavailable, incomplete, or not ready, continue silently at file granularity.

2. NDJSON Update Discipline

  • Keep one valid JSON object per line.
  • Preserve stable key order inside each record.
  • Preserve global line order sorted by axis, then id.
  • Replace only the lines for nodes actually affected by the current run.
  • Do not rewrite untouched lines just to normalize formatting.

3. Node Model

  • Code-axis nodes use axis: "code" with kind: dir | module | file.
  • Doc-axis nodes use axis: "doc" with kind: "doc-section".
  • Code axis detects undocumented code (syncStatus: "missing").
  • Doc axis detects stale or drifted narrative (syncStatus: "drift").
  • New nodes may start with lastSyncedRef: null until first verified sync.

4. Freshness Rules

  • Only mark a node based on evidence gathered in the current run.
  • Leave untouched nodes exactly as they were.
  • For modified files, default conservatively to syncStatus: "drift" until the affected docs are actually reviewed.
  • Never mass-flip nodes to ok because a run completed.

Read the full file on GitHub · 123 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.

  1. 28d ago Changed · +1 lines c473f872f9c1
  2. 1mo ago First seen · 122 lines · 46 tokens per session scan A adc80cb38f46

Subscribe to this mod's changes

doc-sync is a skill published in the GitHub repository monkey1wizard/Golem-Agents-Legion (14 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,521 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-09-04.