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-agent-teamsgit 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-agent-teams)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-teams"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-teams/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-agent-teams"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-teams.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.00059 | $0.01329 |
| Opus 5 | $0.00030 | $0.00665 |
| Sonnet 5 | $0.00012 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
openclaw-agent-teams 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 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.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Design & Operations
Guide the user through designing, building, and operating a production agent team following ClawPort best practices.
Hierarchy Design
Agent teams follow a three-tier hierarchy:
| Tier | Role | Example |
|---|---|---|
| Orchestrator | Top-level coordinator. Routes work, holds team memory, delivers briefings. | Jarvis (reportsTo: null) |
| Team Lead | Owns a domain pipeline end-to-end. Manages a sub-team. | VERA (Strategy), LUMEN (SEO), HERALD (LinkedIn) |
| Specialist | Does one thing well. Reports up, never manages others. | TRACE (Market Research), QUILL (LinkedIn Writer) |
Hierarchy Rules
- One root. Exactly one agent has
"reportsTo": null— the orchestrator. - Team leads own pipelines. Each lead runs end-to-end delivery for their domain.
- Leaf agents are specialists. One job, no scope creep.
- Max depth of 3. Deeper nesting adds latency with little benefit.
- Keep directReports consistent. If B has
"reportsTo": "A", then A'sdirectReportsmust include B.
SOUL.md — Agent Character Documents
Every agent needs a SOUL.md that defines identity, expertise, constraints, and relationships.
# AGENT_NAME -- Role Title
## Identity
Who the agent is. Personality. Communication style.
First-person voice: "I am VERA, the Chief Strategy Officer."
## Expertise
Domains this agent knows deeply.
What it defers to other agents.
## Operating Rules
Hard constraints. What it must always/never do.
Output format requirements.
## Relationships
Reports to. Direct reports. Peer collaborators.
## Memory
What it remembers between sessions.
Where its persistent knowledge lives.
Guidelines:
- Be specific about personality. Distinct voices prevent agents from sounding the same.
- Define what the agent does NOT do. Negative constraints are as important as positive ones.
- Include output format examples. If the agent produces structured data, show the format.
- Keep it under 500 lines. Long SOUL files dilute focus.
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.
- 11d ago First seen · 127 lines · 59 tokens per session scan A 079a62e8c76c
openclaw-agent-teams is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 1,329 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…