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/katopz/katgpt-rs/doc-syncnpx skills add katopz/katgpt-rs --skill doc-syncgit clone --depth 1 https://github.com/katopz/katgpt-rsWrote 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.
[](https://agentmods.dev/skills/katopz/katgpt-rs/doc-sync)<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="Measured on agentmods" height="20"></a>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.00097 | $0.23597 |
| Opus 5 | $0.00048 | $0.11799 |
| Sonnet 5 | $0.00019 | $0.04719 |
| Haiku 4.5 | $0.00010 | $0.02360 |
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 yesterday.
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 — 392 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-callrow REQUIRES an existing issue file; aby-designrow 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-depsprints 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.mdD2/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.
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.
- yesterday First seen · 392 lines · 97 tokens per session scan A 5f4c5b9c0e56
doc-sync is a skill published in the GitHub repository katopz/katgpt-rs (98 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 23,597 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
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…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…