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 skills add TheophilusChinomona/claude-openclaw-plugin --skill openclaw-workspace-wizardgit 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/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-workspace-wizard)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-workspace-wizard"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-workspace-wizard/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/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-workspace-wizard"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-workspace-wizard.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.00116 | $0.02626 |
| Opus 5.5 | $0.00046 | $0.01050 |
| Sonnet 5.5 | $0.00023 | $0.00525 |
| Haiku 4.5 | $0.00012 | $0.00263 |
Grade A, and why
openclaw-workspace-wizard 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 1mo 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Workspace Wizard
The full guided journey for creating a production-ready OpenClaw agent workspace. Chains six phases with user checkpoints between each, so you can pause, adjust, and resume at any point.
Overview
This wizard orchestrates the complete lifecycle:
Phase 1: Discovery → What agent do you need?
Phase 2: Memory Design → How should it remember?
Phase 3: Soul Design → Who is this agent?
Phase 4: Workspace → What files and structure?
Phase 5: Scaffolding → Generate everything
Phase 6: Quality Audit → Score and improve
Each phase produces artifacts that feed the next. You can skip phases if you already have the artifacts (e.g., skip Discovery if you already know exactly what you want).
Phase 0: Welcome and Setup
Configuration
Determine workspace settings:
- Workspace name: What should this agent be called? (working title — can change later)
- Workspace mode: Single agent or multi-agent team?
- Workspace location: Where to create the workspace?
- Default:
~/.openclaw/workspace/(single-agent) - Multi-agent:
~/.openclaw/agents-workspaces/<agent-id>/ - Custom path if user prefers
- Default:
Resume Detection
Check the workspace location for existing artifacts:
- Discovery reports, memory architecture docs, SOUL.md drafts
- If found, present them and offer: [R] Resume from last checkpoint, [S] Start fresh, [P] Pick a specific phase
Welcome Message
"Welcome! Let's build your OpenClaw agent workspace step by step.
Your settings:
- Agent name: {name}
- Mode: {single/multi-agent}
- Output: {workspace path}
This journey has 6 phases. I'll check in with you between each one so you can adjust course. Ready?"
Wait for user confirmation.
Phase 1: Discovery — What Agent Do You Need?
Goal: Understand what the agent does, who it serves, and what it needs.
1.1 Reference Templates
"Before we dive in — would you like to browse reference templates for common agent archetypes? I have templates for Software Architect, Code Reviewer, Security Engineer, Technical Writer, DevOps Automator, Sprint Prioritizer, UX Researcher, and Feedback Synthesizer.
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.
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.
- 1mo ago First seen · 338 lines · 116 tokens per session scan A b36bd853fb85
openclaw-workspace-wizard is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 116 tokens to every session and 2,626 once invoked, about $0.0005 per session on Opus 5.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-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…