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.
git clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/theophiluschinomona/claude-openclaw-plugin/oc-update)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-update"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-update/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/theophiluschinomona/claude-openclaw-plugin/oc-update"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-update.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.00013 | $0.00477 |
| Opus 5 | $0.00006 | $0.00238 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade B, and why
oc-update scanned grade B with 1 finding 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Check if running as correct user (may need sudo for global npm) What it actually says
/oc-update Command
Update OpenClaw to the latest version, verify the installation, and restart the gateway.
Execution
- Check current version:
openclaw --version
- Detect package manager and update:
Check how OpenClaw was installed and update accordingly:
# Check if installed via npm
which npm && npm list -g openclaw 2>/dev/null && echo "NPM_INSTALL"
Then run the appropriate update:
npm (most common):
npm install -g openclaw@latest
Other package managers: Inform the user to use their package manager's update command.
- Verify new version:
openclaw --version
- Run diagnostics:
openclaw doctor
If doctor reports issues, suggest running openclaw doctor --fix.
- Restart gateway:
openclaw gateway restart
- Check status:
openclaw status
Output
Report each step's result:
Update Summary:
Previous version: X.Y.Z
New version: A.B.C
Doctor: ✓ passed (or X issues found)
Gateway: ✓ restarted
Status: ✓ running
If Already Up to Date
OpenClaw is already at the latest version (X.Y.Z).
Running diagnostics to verify health...
Still run doctor and status to confirm everything is healthy.
If Update Fails
- Check if running as correct user (may need sudo for global npm)
- Check network connectivity
- Suggest manual update:
npm install -g openclaw@latest - If gateway won't restart after update: check
openclaw logs --tail 50
After Running
- Suggest running
openclaw security auditafter updates (new checks may be available) - If breaking changes, suggest reviewing the changelog
- Remind about
/oc-backupbefore major version updates
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.
- 10d ago First seen · 92 lines · 13 tokens per session scan B 711dc9217e09
oc-update is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 477 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.