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.
npx agentmods add commands/kevinzai/commander/ccc-openclawgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-openclaw)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-openclaw"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-openclaw.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00849 |
| Opus 5 | $0.00011 | $0.00425 |
| Sonnet 5 | $0.00004 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
ccc-openclaw 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw — Native Platform Integration
Managing OpenClaw integration: {{input}}
Subcommands
/openclaw status
Show OpenClaw gateway status and integration overview:
- Probe gateway at configured URL (default:
http://localhost:18789/health) - Report gateway status, version, uptime
- Show connected agents and their status
- Show synced skill count
- Show active channels
OPENCLAW STATUS:
Gateway: ● Online (v2026.3.24, uptime 4h 23m)
Agents: 38 registered, 12 active
Skills: 280 synced from Kit
Channels: Discord ● Slack ● Telegram ● WhatsApp ●
Last sync: 2m ago
/openclaw sync
Force synchronization of Kit skills and hooks with OpenClaw:
- Discover all skills in
~/.claude/skills/ - Register each with OpenClaw skill registry
- Register Kit hooks with OpenClaw webhook system
- Sync workflow modes as agent profiles
- Report results
OPENCLAW SYNC:
Skills: 280 synced (3 new, 1 updated)
Hooks: 18 registered
Modes: 9 agent profiles generated
Duration: 1.2s
/openclaw configure
Interactive setup for OpenClaw integration:
- Gateway URL: Enter URL or accept default (
http://localhost:18789) - Auto-sync: Enable/disable automatic sync on session start
- Event forwarding: Choose which Kit events to forward to OpenClaw
- Agent binding: Map Kit modes to specific OpenClaw agents
- Save to
bible-config.json
/openclaw health
Comprehensive health check:
- Gateway connectivity and response time
- Each channel status (Discord, Slack, Telegram, WhatsApp, BlueBubbles, WebChat)
- Agent status (active, idle, error, last activity)
- Memory DB health (size, last write, integrity)
- Error log (last 5 errors)
- Cost report (today's spend, budget remaining)
OPENCLAW HEALTH CHECK:
Gateway: ● OK (12ms response)
Discord: ● Connected (5 channels)
Slack: ● Connected (3 workspaces)
Telegram: ● Connected
WhatsApp: ● Connected
Agents: 38/38 healthy
Memory: 965MB (OK)
Errors: 0 in last hour
Cost today: $2.15 / $10.00 limit
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.
- yesterday First seen · 113 lines · 22 tokens per session scan A 9decc18541b6
ccc-openclaw is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 849 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-09-04.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
review
Run a Codex code review of your working tree or a branch (read-only).
adv-codex
Send a prompt to Codex CLI and return the response.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
add-hook
Add a new hook to .claude/settings.json. Quick operation, no full interview needed. Trigger phrases: "add hook", "auto-format on save", "run tests after edit", "lint on write", "run [command] after [tool]".