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/ric03uec/clawrium/sync-upstreamnpx skills add ric03uec/clawrium --skill sync-upstreamgit 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/sync-upstream)<a href="https://agentmods.dev/skills/ric03uec/clawrium/sync-upstream"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/sync-upstream.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.00035 | $0.04653 |
| Opus 5 | $0.00017 | $0.02327 |
| Sonnet 5 | $0.00007 | $0.00931 |
| Haiku 4.5 | $0.00003 | $0.00465 |
Grade A, and why
sync-upstream 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.
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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Upstream
Not to be confused with
clawctl agent sync. That command pushes config/workspace overlays to a running agent and rotates the gateway bearer (#437). This skill is read-only on the local repo and the running fleet — it only queries upstream release feeds and opens GitHub issues for the maintainer.
Recurring maintainer skill. For each tracked agent type (hermes, openclaw, zeroclaw), determine:
- the highest version currently pinned in
src/clawrium/platform/registry/<type>/manifest.yaml - the latest stable (non-prerelease, non-beta, non-alpha) upstream version
- whether (2) is newer than (1)
When (2) > (1) for at least one agent, open:
- One parent issue titled
upstream agent upgrade YYYY-MM-DDthat tracks the whole sync pass. - One child issue per agent with a gap, linked from the parent. Each child contains the upgrade plan AND the per-OS / per-arch test matrix inline as checklist rows — the test matrix is not broken out into grandchild issues.
This skill never edits manifest.yaml, never touches running agents, and never opens PRs. It only reads manifests, queries upstream, and creates issues.
Inputs
$ARGUMENTS(optional): one or more ofhermes,openclaw,zeroclaw. If empty, run all three.
$ARGUMENTS MUST be validated against the literal allow-list {hermes, openclaw, zeroclaw} before being interpolated into any filesystem path or shell command. A single unknown token aborts the run. This is a path-traversal guard — src/clawrium/platform/registry/<t>/manifest.yaml is the only place <t> is consumed, but the inline Python loop teaches the pattern and must not normalize an unsafe value.
Untrusted upstream strings
Every string returned by gh release list, npm view, or any other upstream feed is untrusted input. Before that value is rendered into an issue title, issue body, terminal report, or shell argument:
- Validate against the regex
^[A-Za-z0-9._+-]{1,40}$. Anything else (whitespace, control chars, bidi/zero-width codepoints, RTL overrides, unicode look-alikes) is rejected — log it asupstream-rejected: <agent>and treat the agent as "upstream-unreachable" for this run. - Strip a single leading
vonly if present (hermes / zeroclaw tags); neverlstrip("v")(would mangle a hypotheticalvvv1.0). - After validation, pass through
cli/output/_sanitize.py:sanitize_passthroughfor any value rendered to the terminal, matching the workspace-overlay path's contract.
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.
- today Changed 6de9ccb42ab5
- 4d ago First seen · 332 lines · 35 tokens per session scan A 848df2232076
sync-upstream is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 4,653 once invoked, about $0.0002 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-30.
Other skills, from other repositories
load-github-action-thread
Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.
uv-workflow
Use when a coding agent needs to run Python code, modules, one-liners, tools, tests, or standalone scripts through uv, or create and maintain PEP 723 scripts with uv init/add/remove --script. Avoid direct python/python3 shell entrypoints.
simulate-contracts
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
model-data-schema
Author the persistence schema as a binding contract from the captured external shapes and the interview — before any test stub is written.
author-test-stubs
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
derive-source-stubs
Derive the source stub files (.pyi) from the reviewed tests — every type the tests reference gets a definition.