Borrowing it
Nothing to install: this file belongs to ric03uec/clawrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ric03uec/clawrium/main/.opencode/commands/sync-upstream.mdgit 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/commands/ric03uec/clawrium/sync-upstream)<a href="https://agentmods.dev/commands/ric03uec/clawrium/sync-upstream"><img src="https://agentmods.dev/badge/commands/ric03uec/clawrium/sync-upstream/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/commands/ric03uec/clawrium/sync-upstream"><img src="https://agentmods.dev/badge/commands/ric03uec/clawrium/sync-upstream.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.00031 | $0.00240 |
| Opus 5.5 | $0.00012 | $0.00096 |
| Sonnet 5.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 2mo 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.
- 2mo ago First seen · 23 lines · 31 tokens per session scan A 7ee114513565
sync-upstream is a command published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 13d ago), licensed Apache-2.0. It adds 31 tokens to every session and 240 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 commands, from other repositories
cli-anything-web:list
List all available CLI-Anything-Web CLIs (installed and generated).
rad-migrate
Migrate a YouTube channel to Rad TV.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.