doc-sync

A one-way publishing tool that copies files from a project's design/ directory into a ticket or project documentation system such as a GitHub wiki or Linear Docs. It can remove documentation pages that no longer have matching source files.

In plain words
What is it for?
Use it to publish design documents, read the chosen backend from .project-conf.toml, and prune orphaned pages in GitHub wiki or Linear Docs.
Why use it?
It keeps the external documentation store aligned with the files maintained in the project. The original design/ files remain unchanged.

Skill for Claude CodeCodex

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/iansmith/slopstop/doc-sync
Any agent
npx skills add iansmith/slopstop --skill doc-sync
Clone the repo
git clone --depth 1 https://github.com/iansmith/slopstop

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00053 $0.00722
Opus 5 $0.00026 $0.00361
Sonnet 5 $0.00011 $0.00144
Haiku 4.5 $0.00005 $0.00072

Measured 2d ago against content hash 09f55c44f1bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

skills/doc-sync/SKILL.md · 66 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

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

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. 2d ago First seen · 66 lines · 53 tokens per session scan A 09f55c44f1bf

Subscribe to this mod's changes

doc-sync is a skill published in the GitHub repository iansmith/slopstop (2 stars, last pushed 2d ago), with no licence file. It adds 53 tokens to every session and 722 once invoked, about $0.0003 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.