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-cron)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-cron"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-cron/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-cron"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-cron.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.00015 | $0.00691 |
| Opus 5 | $0.00008 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
oc-cron 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 12d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-cron Command
Manage cron job scheduling — list jobs, create new ones, trigger manual runs, and view history.
Arguments
The user provides: $ARGUMENTS
Parse:
- subcommand (required):
status,list,add,run,runs,remove - jobId (required for
run,runs,remove): the cron job identifier
Subcommands
status
Show scheduler status:
openclaw cron status
Report: enabled/disabled, number of configured jobs, currently running jobs, and maxConcurrentRuns setting.
list
List all configured cron jobs:
openclaw cron list
Format output as a table with columns: Job ID, Schedule, Agent, Status (enabled/disabled), Last Run.
add
Guide the user through creating a new cron job:
- Ask for a job ID (lowercase slug, e.g.,
daily-briefing) - Ask for a schedule in crontab syntax (e.g.,
0 8 * * *for daily at 8am) - Ask for the agent ID (default:
main) - Ask for the task description (what the agent should do)
- Ask if the result should be delivered to a chat session
Then run:
openclaw cron add
Or help them add via config if CLI is unavailable.
run <jobId>
Manually trigger a cron job:
openclaw cron run <jobId>
Report the run status and any immediate output.
runs <jobId>
View run history for a specific job:
openclaw cron runs <jobId>
Format output showing: Run ID, Start Time, Duration, Status (success/error), and truncated output.
remove <jobId>
Remove a cron job (with confirmation):
- Show the job details first
- Ask the user to confirm removal
- Run:
openclaw cron remove <jobId>
No subcommand or unrecognized
Show usage help:
Usage: /oc-cron <subcommand> [args]
status Scheduler status
list List all cron jobs
add Create a new cron job (guided)
run <jobId> Manually trigger a job
runs <jobId> View run history
remove <jobId> Remove a job (with confirmation)
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.
- 12d ago First seen · 105 lines · 15 tokens per session scan A 6c53250d0ba5
oc-cron is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 691 once invoked, about $0.0001 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-31.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.