openclaw-agent-planner

openclaw-agent-planner is a skill for Claude Code from TheophilusChinomona/claude-openclaw-plugin. It costs 171 tokens per session (3,595 once invoked), scanned B, original, MIT.

A planning guide for designing OpenClaw agents, which are software assistants, and teams of agents that work together. It helps turn an idea into defined roles, permissions, boundaries, and documentation.

In plain words
What is it for?
Use it to discover agent needs, design single-agent or multi-agent setups, define responsibilities and permissions, and produce team documentation.
Why use it?
It prevents teams from adding agents without deciding what each one should do, what it may access, or how the agents should coordinate.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md; built for openclaw.

Part of the openclaw plugin — 31 skills, 22 commands, 4 agents, 3 hooks shipped together

Good fit Use it to discover agent needs, design single-agent or multi-agent setups, define responsibilities and permissions, and produce team documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner
Install

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.

Any agent
npx skills add TheophilusChinomona/claude-openclaw-plugin --skill openclaw-agent-planner
Clone the repo
git clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-plugin

Made for: Claude Code.

Or install openclaw, the plugin that ships this one along with the rest of its 31 skills, 22 commands, 4 agents, 3 hooks.

Wrote 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.

agentmods badge for openclaw-agent-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner/github.svg)](https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner)
Your own site
<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-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.

agentmods 80×15 button for openclaw-agent-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 171 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,595 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00171 $0.03595
Opus 5 $0.00086 $0.01798
Sonnet 5 $0.00034 $0.00719
Haiku 4.5 $0.00017 $0.00360

Measured 11d ago against content hash 57e5226f6edb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

openclaw-agent-planner scanned grade B with 1 finding 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

[chmod 444 on identity files, git backup, etc.]
plugins/openclaw/skills/openclaw-agent-planner/SKILL.md · 386 lines

How it starts

The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenClaw Agent Planner

Brainstorm, design, and fully document OpenClaw agents — from a single personal assistant to a coordinated multi-agent team.

Why This Skill Exists

Most people start with one agent and eventually realize they need several — a personal assistant, a DevOps bot, a research agent, a sales development agent, etc. The hard part isn't installing them; it's deciding what each one does, what it's allowed to do, and how they interact. This skill walks through that design process and produces real documentation at the end.

Workflow Overview

The skill runs in three stages:

Stage 1: Discovery    →  Understand the user's world (roles, tools, workflows, pain points)
Stage 2: Design       →  Brainstorm agents, define capabilities, draw boundaries
Stage 3: Document     →  Produce comprehensive Agent Team Documentation

Each stage is interactive — ask questions, listen, synthesize, confirm, iterate.


Stage 1: Discovery — Understanding the User's World

Before proposing any agents, understand the landscape. Ask questions across these dimensions:

1.1 Role & Context

  • What do you do? (job title, industry, daily responsibilities)
  • What teams or people do you work with?
  • What's your tech stack and tooling? (platforms, services, communication channels)
  • What recurring workflows eat your time?

1.2 Pain Points & Automation Appetite

  • What tasks do you wish someone else would handle?
  • What falls through the cracks regularly?
  • Where do you lose time to context-switching?
  • What would you trust an AI agent to do unsupervised? What would you NOT trust it with?

1.3 Existing Setup

  • Do you already have any OpenClaw agents running? If so, what do they do?
  • What channels are you using? (WhatsApp, Telegram, Discord, iMessage, web)
  • What tools/MCP servers do you have access to? (calendar, email, web search, file systems, APIs)
  • Any existing automation (cron jobs, scripts, Zapier, n8n)?

1.4 Constraints

  • Budget sensitivity? (model costs — Claude Opus vs Sonnet vs Haiku for different agents)
  • Security requirements? (data handling, credential access, network boundaries)
  • Uptime needs? (always-on vs on-demand)
  • Who else will interact with these agents? (just you, your team, clients, public?)

Read the full file on GitHub · 386 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 11d ago First seen · 386 lines · 171 tokens per session scan B 57e5226f6edb

Subscribe to this mod's changes

openclaw-agent-planner is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 171 tokens to every session and 3,595 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens