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-security)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-security"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-security/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-security"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-security.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.00419 |
| Opus 5 | $0.00000 | $0.00210 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
oc-security 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 9d 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
/oc-security Command
Run an OpenClaw security audit, group findings by severity, and optionally auto-fix issues.
Arguments
The user provides: $ARGUMENTS
Parse optional flags:
--deep— include live Gateway probe--fix— auto-fix supported findings--json— output raw JSON (for scripting)
Execution
- Run the security audit:
openclaw security audit $ARGUMENTS
- Parse and group findings by severity:
CRITICAL
Show critical findings first with red emphasis. For each:
- Finding: description of the issue
- Risk: why it matters
- Fix: exact command or config change to resolve
WARNING
Show warnings next. Same format as critical but lower urgency.
INFO
Show informational items last. Brief description + recommendation.
- After showing findings, provide a summary:
Security Audit Summary:
Critical: X findings
Warning: Y findings
Info: Z findings
- If
--fixwas used, report which fixes were applied automatically.
If No Findings
Report a clean audit:
✓ Security audit passed — no findings.
Suggest running --deep for a more thorough check.
If OpenClaw Not Installed
Guide the user to install OpenClaw first:
OpenClaw CLI not found. Run /oc-setup to install.
After Running
- For critical findings: urge immediate action, offer to apply fixes
- For
--fix: verify fixes with a re-run:openclaw security audit - Suggest scheduling periodic audits (e.g., after config changes or updates)
- For hardening guidance: reference the
openclaw-securityskill
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.
- 9d ago First seen · 73 lines · 0 tokens per session scan A c5e320a82e48
oc-security 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 419 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.