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-planner)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-planner"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-planner/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-planner"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-planner.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.00024 | $0.00558 |
| Opus 5 | $0.00012 | $0.00279 |
| Sonnet 5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
oc-planner 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-planner Command
Run the openclaw-agent-planner skill to brainstorm, design, and document OpenClaw agent teams, then produce Agent Team Documentation.
Arguments
The user provides: $ARGUMENTS
Parse:
- output-path (optional): Where to write the generated markdown document. If omitted, write to the current workspace or ask the user.
Skill Reference
Apply the full workflow from the openclaw-agent-planner skill (under skills/openclaw-agent-planner/SKILL.md).
Stage 1: Discovery
Understand the user's world: role & context, pain points & automation appetite, existing setup, constraints. Ask focused questions; don't re-ask what you can infer.
Stage 2: Design
- 2.1 Agent brainstorm: Propose a table of agents (Name, Role, Why, Channel). Refine with the user (must-haves, overlaps, gaps, priority).
- 2.2 Capability mapping: For each agent, build a permission matrix (Autonomous / Confirm / Restricted / Denied). Use references/permissions-reference.md in the planner skill for capability categories and archetype profiles (Personal Assistant, DevOps, Sales Dev, Research, SHEQ).
- 2.3 Inter-agent design: If multiple agents, define communication, delegation, shared vs isolated resources, conflict resolution. Recommend the OpenClaw multi-agent pattern (per-agent workspace, shared AGENTS.md).
- 2.4 Model selection: Recommend Opus/Sonnet/Haiku per agent based on task and cost.
Stage 3: Document
Generate the Agent Team Documentation with the exact structure in the skill: Team Overview, Agent Profiles (per agent: role, persona, capabilities, boundaries, workflows, memory strategy, goals, config snippet), Team Interaction Rules, Security & Governance, Implementation Roadmap, Appendix.
Save as markdown at the given output path. If the user wants .docx, use the docx skill to produce a formatted Word document.
Quality Checks
Before delivery, verify: every agent has a full profile; permission levels are consistent; no orphan agent references; roadmap has concrete steps; security covered; persona aligns with role.
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 · 48 lines · 24 tokens per session scan A 28a3079032d6
oc-planner is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 558 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
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.