agentmods.dev

katgpt-rs: Skill for Claude Code

.agents/skills/doc-sync/SKILL.md

doc-sync is a skill for Claude Code, Codex from katopz/katgpt-rs. It costs 97 tokens per session (17,445 once invoked), scanned A, original, MIT.

A documentation-maintenance skill that compares committed repository changes with the latest entries in `.docs/`, `README.md`, and `BOUNDARY.md`. It identifies work that has landed but is not yet documented.

In plain words
What is it for?
Use it after a plan succeeds, issues are closed, a feature changes status, or during a quarterly documentation check. It updates the affected documentation across workspace repositories.
Why use it?
It helps prevent repository documentation from falling behind the code and issue status. It is intended for completed work, not planned or speculative changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is katopz/katgpt-rs's own configuration. It tells Claude Code and Codex how to work on katgpt-rs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything katgpt-rs configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/katopz/git.

not rated 140repo changed today A scan 97 tokens original MIT
View source ↗ katopz/katgpt-rs
Reuse

Borrowing it

Nothing to install: this file belongs to katopz/katgpt-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/katopz/katgpt-rs/develop/.agents/skills/doc-sync/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/katopz/katgpt-rs

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/katopz/katgpt-rs/doc-sync/github.svg)](https://agentmods.dev/skills/katopz/katgpt-rs/doc-sync)
Your own site
<a href="https://agentmods.dev/skills/katopz/katgpt-rs/doc-sync"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/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/katopz/katgpt-rs/doc-sync"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/doc-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 17,445 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.00097 $0.17445
Opus 5.5 $0.00039 $0.06978
Sonnet 5.5 $0.00019 $0.03489
Haiku 4.5 $0.00010 $0.01744

Measured today against content hash cd64a0d79c74, 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 today.

The scan reads SKILL.md. This mod also ships 3 executable files (tools/link_fix.py, tools/linkcheck_sweep.py, tools/sync_commit.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/doc-sync/SKILL.md · 399 lines

How it starts

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

doc-sync — Keep .docs/ + README.md in sync with landed work

This skill brings a repo's documentation up to date with the work that has landed in git but not yet been written up. It is the doc equivalent of a cargo doc rebuild: the code shipped, now make the narrative match.

When to use

  • After a plan closes with a GOAT/gain verdict (promote, keep-opt-in, or honest fail).
  • After a batch of issues resolves (especially negative-result issues that move a primitive's status line).
  • After a feature is promoted to default-on OR demoted to opt-in.
  • Quarterly as a doc-hygiene gate.
  • NOT for speculative work — only landed, committed work counts.

BOUNDARY.md — the 4th doc surface (added 2026-08-21)

Every repo ships a root BOUNDARY.md: Owns / Does not own / May depend on (crate-granular allowlist) / Inherited (links) / Drift ledger. It is a doc-sync surface because its drift ledger is a claim about issue state, and claims rot:

  • Row ⟺ open issue. A fixable / owner-call row REQUIRES an existing issue file; a by-design row cites a decision record instead. When an issue closes, its row must be removed in the same commit — the noise-reduction rule extended to BOUNDARY.md. A row whose issue is gone is the boundary equivalent of a stale README claim.
  • Flag row-without-issue and issue-without-row (a boundary issue that landed with no ledger row is invisible to the guard).
  • Don't hand-verify the dep tables — run riir-ai/scripts/ci_boundary_contract.sh. It fails on an undeclared cross-repo dep, a stale allowlist row, an unparseable ledger, and on the 4 split-prep invariants. --list-deps prints the measured graph.
  • Numbers in a contract are measurements, so they carry a date. If a row cites "N symbols" or "N packages", re-measure before trusting it in a new decision (riir-ai/BOUNDARY.md D2/D3 are the pattern).
  • The contract is per-repo; cross-repo rules live in ONE canonical home (chain admission → riir-chain, dep matrix + split-prep → riir-ai) and every other repo LINKS. Never copy a cross-repo rule into a second file — that is the duplication doc-sync exists to catch.

Read the full file on GitHub · 399 lines

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. today Changed cd64a0d79c74
  2. yesterday Changed · +1 lines 982613778937
  3. 2d ago Changed · -3 lines 7b6430c57074
  4. 3d ago Changed · +2 lines 3855ab7c0875
  5. 4d ago Changed · +18 lines b995a61a144c
  6. 5d ago Changed · +5 lines 14e8fc69f2b0
  7. 6d ago Changed · +28 lines d06b917a0c41
  8. 7d ago Changed · +1 lines ab78e51d119e
  9. 8d ago Changed · +1 lines 384d19c49a94
  10. 9d ago First seen · 346 lines · 97 tokens per session scan A c5e44064a04c

Subscribe to this mod's changes

doc-sync is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 17,445 once invoked, about $0.0004 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-03.

CommitsGit and workflowWriting and docs
Related

Other skills, from other repositories

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens