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 commands/ric03uec/clawrium/sync-upstreamgit clone --depth 1 https://github.com/ric03uec/clawriumWhat 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.00031 | $0.00240 |
| Opus 5 | $0.00015 | $0.00120 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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 3d 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.
What it actually says
Run the upstream-version sync pass for tracked agent types.
$ARGUMENTS
See .opencode/skills/sync-upstream/SKILL.md for the full skill — it
holds the upstream lookup commands (GitHub release list for hermes /
zeroclaw, npm view openclaw dist-tags.latest for openclaw), the
manifest-pin parser, the de-dup rules, and the parent + child issue
body templates.
This command is read-only on the local repo and the running fleet —
it never edits manifest.yaml, never restarts agents, never opens PRs.
It only opens GitHub issues, and only after the user types the literal
token open-issues at the confirmation prompt.
If $ARGUMENTS is non-empty, restrict the sync to the listed agent
types — each token MUST match the allow-list {hermes, openclaw, zeroclaw} exactly. Any other value aborts the run.
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.
- 3d ago First seen · 23 lines · 31 tokens per session scan A 7ee114513565
sync-upstream is a command published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 15d ago), licensed Apache-2.0. It adds 31 tokens to every session and 240 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
submit_to_list
Fork an external GitHub repo, add an entry to a curated list (e.g. awesome-), and open a PR — all via gh CLI.