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 ric03uec/clawrium --skill docs-syncgit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/ric03uec/clawrium/docs-sync)<a href="https://agentmods.dev/skills/ric03uec/clawrium/docs-sync"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/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/ric03uec/clawrium/docs-sync"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00662 |
| Opus 5.5 | $0.00011 | $0.00265 |
| Sonnet 5.5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-sync
Once per day, find code changes that altered user-visible behavior and
propose corresponding updates to docs/ and scenarios/. The goal is
that anyone running the documented commands or following the scenarios
hits the same surface real users hit today.
Inputs
git log --since='24 hours ago' --first-parent mainfor the commit set (first-parent skips merge-squash internals when present).git diff <prev>..<head>per logical change.- The current state of
docs/andscenarios/.
Triage rule — what counts as "user-visible"
Include a change in scope when any of the following is true:
- Adds, renames, removes, or changes the signature of a
clawctlCLI command or option (src/clawrium/cli/). - Changes a documented config path or env var.
- Changes an installation, configuration, or onboarding stage.
- Changes a GUI route, control, or visible label.
- Changes output of a
clawctl ps-style status command in a way a user would notice.
Exclude pure refactors, test-only changes, dependency bumps that do not change observable behavior, and internal log strings.
Output
For each cluster of related changes, open one PR titled:
docs(<area>): sync with <one-line behavior change>
PR contents:
- Doc edits limited to the surface that actually changed.
- Scenario updates limited to scenarios the change actually breaks.
- Hard cap: 2 new scenarios per run. Prefer updating an existing scenario over adding a new one. If you would exceed the cap, leave a TODO comment in the PR body listing the deferred scenarios.
Hard constraints
- Do not edit
docs/purely for tone or grammar — out of scope. - Do not touch
AGENTS.md,CLAUDE.md, or.itx/from this skill. - If the diff is unclear, open the PR anyway with
[draft]in the title and request input from the author of the originating commit (one short PR-body line: "@ — please confirm the user-facing wording"). - Never merge your own PRs. The PR opens against
mainand waits for human review.
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.
- 1mo ago First seen · 76 lines · 27 tokens per session scan A d1e6188aa9e8
docs-sync is a skill published in the GitHub repository ric03uec/clawrium (67 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 662 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-30.
Other skills, from other repositories
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…