O

OpenCode Orchestrator

agnusdei1207/opencode-orchestrator · v2.0.21 · 85fd256 · Development & Workflow

by agnusdei1207Scan grade: Acceptable

Multi-agent mission control for OpenCode with Commander, Planner, Worker, and Reviewer workflows

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is OpenCode Orchestrator a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • OpenCode

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • The publisher has not verified ownership on HOL.
  • No license declared in the manifest.

What is OpenCode Orchestrator?

OpenCode Orchestrator is a published development & workflow plugin for AI coding agents in the OpenCode ecosystem, developed by agnusdei1207 and distributed through the HOL AI plugin registry. Multi-agent mission control for OpenCode with Commander, Planner, Worker, and Reviewer workflows.

Canonical slug
agnusdei1207/opencode-orchestrator
Version
v2.0.21 · 85fd256 · updated Nov 2, 2026

Registry snapshot

Support the project
GitHub Sponsors
Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
Yes

Trust and security

Trust & reputation

72

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
85/100
MCP server setup
100/100
Plugin Security
74/100
Provenance
70/100
Publisher Quality
75/100

Provenance

Plugin root
.
Source repo
https://github.com/agnusdei1207/opencode-orchestrator
Source commit
85fd256f7b9b…
Publisher verified
No
Owner verified
Not owner verified
Agent Plugins 1.0
Not detected

Continuous scanner CI not detected

This plugin remains listed. Its overall trust score is reduced by 10% because security checks are not maintained in the source repository's CI.

Optional: maintain the scanner in the source repository's CI to receive the full trust score. Listing does not require that change.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Needs review
Security result
74
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
C · Acceptable
Version
3.24.2
cisco-skill-scanner: skippedcisco-mcp-scanner: skipped

Manifest Validation

21/31

9 checks

Security

13/16

9 checks

Operational Security

3/6

5 checks

Best Practices

6/9

5 checks

Marketplace

N/A

3 checks · not applicable

Skill Security

N/A

3 checks · not applicable

Code Quality

10/10

2 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

lowsecuritySECURITY_MD_MISSING

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_AUTHOR

The manifest is missing the documented recommended field "author".

Add "author" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_LICENSE

The manifest is missing the documented recommended field "license".

Add "license" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_KEYWORDS

The manifest is missing the documented recommended field "keywords".

Add "keywords" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_SHORTDESCRIPTION

The interface object is missing a valid "shortDescription" value.

Add a valid "shortDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_LONGDESCRIPTION

The interface object is missing a valid "longDescription" value.

Add a valid "longDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Source

Install v2.0.21 from a native release archive or pinned source.

Install guide
  1. 1

    Download the release archive

    Use the v2.0.21 archive. That tag is a different source revision from later commits on the default branch.

    shell
  2. 2

    Or install the pinned Cargo source

    Pinned Git source. Check the publisher install guide before using a package registry.

    shell
  3. 3

    Follow the publisher install guide

    https://github.com/agnusdei1207/opencode-orchestrator/blob/v2.0.21/docs/INSTALL.md

Did setup work in Source?

No setup reports for Source yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W46, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "name": "opencode-orchestrator",
  "version": "2.0.21",
  "description": "Multi-agent mission control for OpenCode with Commander, Planner, Worker, and Reviewer workflows",
  "repository": "https://github.com/agnusdei1207/opencode-orchestrator",
  "homepage": "https://github.com/agnusdei1207/opencode-orchestrator",
  "interface": {
    "displayName": "OpenCode Orchestrator",
    "developerName": "agnusdei1207",
    "category": "Development & Workflow"
  },
  "holPackageManager": "cargo",
  "holReleaseTag": "v2.0.21",
  "holAssessedCommit": "85fd256f7b9be301c326af1ab50a30b323e97675",
  "holManifestOrigin": "synthesized",
  "registryIndexVersion": 9
}

File inventory

.codex-plugin/plugin.json

plugin-manifest

595 bytes

7ee2b1de678ed006…

AGENTS.md

file

9,195 bytes

115462e648f2bfb4…

Cargo.lock

file

3,201 bytes

fcbf2952461698cc…

Cargo.toml

file

552 bytes

5b25b2d27eaa102b…

LICENSE

file

1,428 bytes

36c3457c28eb5f65…

package-lock.json

file

219,250 bytes

d3153f9c5afecff1…

package.json

file

3,230 bytes

0c1dd1b08fd98a2e…

README.md

file

4,324 bytes

b04cd0dc155754d8…

README.md

file

4,324 bytes

b04cd0dc155754d8…

tsconfig.json

file

406 bytes

300aa92622c2838a…

OpenCode Orchestrator — Frequently asked questions

What is OpenCode Orchestrator?
OpenCode Orchestrator is an AI plugin in the HOL registry. Multi-agent mission control for OpenCode with Commander, Planner, Worker, and Reviewer workflows.
How do I install OpenCode Orchestrator?
Install OpenCode Orchestrator in your harness: Source — https://github.com/agnusdei1207/opencode-orchestrator/releases/tag/v2.0.21. Full step-by-step guidance is on the HOL plugin page.
How do I install OpenCode Orchestrator in Source?
To install OpenCode Orchestrator in Source, start with https://github.com/agnusdei1207/opencode-orchestrator/releases/tag/v2.0.21. The complete step-by-step install guide for Source is on the HOL plugin page.
How is the Trust Score for OpenCode Orchestrator computed?
OpenCode Orchestrator has a HOL Trust Score of 72 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/agnusdei1207%2Fopencode-orchestrator/trust
Who publishes OpenCode Orchestrator?
OpenCode Orchestrator is published by agnusdei1207 and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W46. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.

Reviews and similar plugins