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-autonomy)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-autonomy"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-autonomy/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-autonomy"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-autonomy.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.00000 | $0.01916 |
| Opus 5 | $0.00000 | $0.00958 |
| Sonnet 5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
oc-autonomy 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 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.
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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-autonomy — Agent Autonomy Audit
Score how well your OpenClaw agents operate autonomously and get actionable remediations.
Before you begin
Load the openclaw-autonomy-audit skill for the full scoring rubric and remediation patterns:
- Scoring rubric:
plugins/openclaw/skills/openclaw-autonomy-audit/SKILL.md - Remediation templates:
plugins/openclaw/skills/openclaw-autonomy-audit/references/autonomy-patterns.md
Scan procedure
Step 1: Identify target agents
If --agent <id> is provided, audit only that agent. Otherwise, discover all agents:
# List all configured agents
openclaw agent list
# Or scan workspace directories
ls -d */SOUL.md 2>/dev/null || ls -d */IDENTITY.md 2>/dev/null
Step 2: Run the 8-item audit for each agent
For each agent, perform these checks and score 0–2 per item:
Check 1: SOUL.md autonomous behavior rules
# Read the agent's SOUL.md
cat <agent-workspace>/SOUL.md
Score:
- 0 — No
## Autonomous Behaviorsection, no keywords like "proactively", "when idle", "periodically", "without being asked" - 1 — Has section but rules are vague (e.g., "be helpful", "check things occasionally")
- 2 — Explicit idle triggers with specific actions: "when idle, do X", "every N minutes, check Y"
Check 2: Scheduling mechanism
openclaw cron list
openclaw config get heartbeat
Score:
- 0 — No cron jobs AND no heartbeat configured
- 1 — Has cron jobs OR heartbeat, but not both
- 2 — Cron for clockwork tasks + heartbeat for judgment-based tasks
Check 3: HEARTBEAT.md actionable checklist
cat <agent-workspace>/HEARTBEAT.md
Score:
- 0 — File missing or empty (only comments/placeholders)
- 1 — Has content but no
- [ ]checklist items (just prose) - 2 — Mission-specific
- [ ]checklist items with clear done criteria
Check 4: Session clearing strategy
openclaw config get session.reset
openclaw config get cron.sessionRetention
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 · 228 lines · 0 tokens per session scan A 6b5c9f3827d7
oc-autonomy is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,916 tokens. 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
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.