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 skills add uwuclxdy/agenticat --skill docs-syncgit clone --depth 1 https://github.com/uwuclxdy/agenticatWrote 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/uwuclxdy/agenticat/docs-sync)<a href="https://agentmods.dev/skills/uwuclxdy/agenticat/docs-sync"><img src="https://agentmods.dev/badge/skills/uwuclxdy/agenticat/docs-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.
<a href="https://agentmods.dev/skills/uwuclxdy/agenticat/docs-sync"><img src="https://agentmods.dev/badge/skills/uwuclxdy/agenticat/docs-sync.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.01628 |
| Opus 5.5 | $0.00010 | $0.00651 |
| Sonnet 5.5 | $0.00005 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
docs-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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Sync
Reconcile prose with code. Every claim in the docs must match what the code does today. Accuracy pass only; no restructuring.
Delegate by default: spawn the docs-reconciler agent (one per repo) and pass it the change description if the pass is scoped. Outside a docs-reconciler lane, run inline only for a single small doc; a docs-reconciler lane never hands the pass to another docs-reconciler. If that agent def is missing in this environment, run the pass inline rather than blocking or trying to create it; the agent is an optional context-saver, not a prerequisite.
Scope
README.md,wiki/,docs/*.md,CLAUDE.md/AGENTS.md(gitignored, still sync them).wiki/+README.mdare the default committed, user-facing docs.- Agent-visible prompt files that enumerate a tool's surface: the
plugin/,commands/,agents/dirs plus skill and agent prompt.md. A prompt that lists a tool's response fields or flags breaks silently when that surface changes, since the model keeps following it and reading fields that no longer exist. Sweep these on any output-shape or API change (field renames, dropped flags), alongsideREADMEanddocs. - Other repo-root docs (
CONTRIBUTING.md,SECURITY.md,.github/*.md, etc.) are in scope only for the parts that make code-derived claims (build/test commands, flags, supported versions). Pure-policy prose with no code claim (CODE_OF_CONDUCT.md, license text, a security-reporting address) is out of scope, same reasoning as code comments below. - Not in scope: code comments (including doc-comments like docstrings, JSDoc, rustdoc; those track code but are the code author's surface, not a doc file), CHANGELOG/release notes (a release-notes convention owns those), README section structure (a readme convention owns that), and bare copyedits (a typo or wording fix carrying no code-derived claim needs a plain edit, not a reconciliation pass).
Procedure
Never run this from a worktree. git worktree add checks out tracked files only; gitignored docs/, CLAUDE.md, .claude/ exist in the main checkout alone, so a pass spawned into a worktree finds nothing to reconcile and reports a false clean. Run from the main checkout. a lane that must not write the main checkout (lane-write bans, unrelated main-owned edits) works read-only against it: it reads the main-checkout docs, produces the corrected text as a patch (diff -u) or wrong->right pairs, and the main session applies them; a lane never edits a main-checkout path.
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.
- 13d ago Changed ce887781823c
- 1mo ago Changed 1e0ef7d88edb
- 1mo ago Changed 6aa97e36dadb
- 1mo ago First seen · 58 lines · 24 tokens per session scan A 346109d07733
docs-sync is a skill published in the GitHub repository uwuclxdy/agenticat (7 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 1,628 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
meta-harness
Run a Meta-Harness-style optimization loop NATIVELY — automatically search over the scaffolding around a FIXED base model (memory, retrieval, context construction, prompt templates, summarization, tool-selection logic) by proposing candidate variants, scoring each on a cheap deterministic eval, and keeping a Pareto…
meta-harness-proteus
Run one iteration of proteus memory-summary evolution. Called by metaharness.py.
gbg
Convert any plan, PRD, feature idea, or brief into a sequenced goal-by-goal execution document with reviewer-gated commits — for everyday feature development, MVPs, migrations, refactors, and hardening alike. Generates a project brief, per-goal scope/tasks/acceptance criteria, an LLM-reviewer prompt (Codex/etc.), a…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".