OpenOPC is a system for building and operating an AI-run company, where specialized AI workers are recruited, assigned tasks, and organized into roles. It is for people who want automated task delegation, collaboration, and organizational learning through AI agents.
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 skills/hkuds/openopc/opc_collabnpx skills add HKUDS/OpenOPC --skill opc_collabgit clone --depth 1 https://github.com/HKUDS/OpenOPCWrote 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/hkuds/openopc/opc_collab)<a href="https://agentmods.dev/skills/hkuds/openopc/opc_collab"><img src="https://agentmods.dev/badge/skills/hkuds/openopc/opc_collab.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.00049 | $0.03655 |
| Opus 5 | $0.00024 | $0.01827 |
| Sonnet 5 | $0.00010 | $0.00731 |
| Haiku 4.5 | $0.00005 | $0.00365 |
Grade A, and why
opc-collab 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 5d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenOPC company-mode collaboration
You are running inside an OpenOPC "company mode" run as one of several agents
collaborating on a larger task. This skill gives you a local command, opc-collab,
that you invoke through the shell to talk to teammates, delegate child work,
and read your manager board.
The CLI is on your PATH. Every invocation reads its identity (who you are,
which project/session, which task) from environment variables that OpenOPC
already set for you before launching this process — you do NOT pass those.
When to use this skill
- You need to message another role (DM, broadcast, or blocking question).
- Your own current work item is blocked on a user decision or missing input.
- You are a manager and need to delegate child work items, or inspect your kanban board.
- You are in a meeting and need to respond or finalize a decision.
- You want to propose a runtime task adjustment (replan).
Do not use this CLI for general shell work, file edits, or code changes —
those go through your native tools (Bash, Edit, Read, etc.).
How to call it
General form:
opc-collab <tool> --args-json-file args.json
All arguments go in the JSON object. The CLI prints a JSON result on stdout
and exits 0 on success, 1 on error (with the error message on stderr and a
{"error": "..."} body on stdout).
Prefer --args-json-file or --args-stdin over inline JSON. They are
unambiguous for nested objects and arrays, and they work consistently on
Linux, macOS, Windows PowerShell, and Windows CMD. If OPC_COLLAB_CLI is set,
use that executable path; otherwise use opc-collab from PATH.
In OpenOPC-spawned Windows runs, do not use --args-json or pipe JSON into
--args-stdin; command-line and PowerShell pipeline text can corrupt non-ASCII
before it reaches the CLI. Write the JSON object to a UTF-8 file and call
opc-collab <tool> --args-json-file <file> instead.
PowerShell-safe UTF-8 file write:
$enc = New-Object System.Text.UTF8Encoding $false; [System.IO.File]::WriteAllText($path, $json, $enc).
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.
- 5d ago First seen · 362 lines · 49 tokens per session scan A ff979e354378
opc-collab is a skill published in the GitHub repository HKUDS/OpenOPC (1,614 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 3,655 once invoked, about $0.0002 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-30.
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…
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…
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…