Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add asfbay-bit/opchain-skills/plugin install opchainWrote 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/asfbay-bit/opchain-skills/oc-orchestrator)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-orchestrator"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-orchestrator/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/asfbay-bit/opchain-skills/oc-orchestrator"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-orchestrator.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.00103 | $0.09940 |
| Opus 5 | $0.00051 | $0.04970 |
| Sonnet 5 | $0.00021 | $0.01988 |
| Haiku 4.5 | $0.00010 | $0.00994 |
Grade A, and why
oc-orchestrator 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 7d 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 — 997 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Pipeline coordinator for the opchain dev ecosystem. This skill does NOT build, audit, deploy, or design — it reads every other skill's checkpoints, maintains a project registry, and answers three questions:
- Where am I? — Cross-skill status across all registered projects.
- What's next? — The single highest-priority action based on pipeline position.
- Route me. — Smart dispatch to the right skill based on intent.
This is an additive layer. Every existing skill retains its own welcome protocol and works independently. The oc-orchestrator provides a better front door and a unified view across projects — it doesn't replace any skill's internal logic.
/oc-ops — Command Reference
ORCHESTRATOR COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STATUS
/oc-ops Show all projects + active skill state
/oc-ops status Same as /oc-ops — full status dashboard
/oc-ops status [project] Status for one project (all skills)
ROUTING
/oc-ops next Recommend the single highest-priority action
/oc-ops next [project] Next action for a specific project
/oc-ops route [intent] Route a vague request to the right skill + phase
PROJECT REGISTRY
/oc-ops projects List all registered projects with health
/oc-ops register Register a new project (path + name)
/oc-ops unregister Remove a project from the registry
/oc-ops switch [project] Set the active project for this session
/oc-ops scan Auto-discover projects by scanning workspace
PIPELINE
/oc-ops pipeline Show the canonical pipeline DAG
/oc-ops pipeline [project] Show where a project sits in the pipeline
/oc-ops blockers Show all blockers across all projects
/oc-ops recent Last-known state per skill (sorted by recency)
META
/oc-ops health Self-check: are all skill files accessible?
/oc-ops skills List all installed opchain skills with versions
/checkpoint Show oc-orchestrator state (registry + session, from the tracked checkpoint)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command, or just describe what you need.
What ships with it
3 files 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.
- 7d ago Changed a95a711e7042
- 10d ago First seen · 997 lines · 103 tokens per session scan A 604feca57f80
oc-orchestrator is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 103 tokens to every session and 9,940 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.