Q Orchestrate
Deterministic, event-driven multi-agent orchestration for software architecting: an Opus dispatcher, domain-scoped sub-agents, and a SQLite ledger instead of markdown state.
Works with: Claude Code (native)
native: this artifact type is that client's own format
Category: Dev Tools & CI — see all ranked ›
Install (Claude Code):
/plugin marketplace add Darkri-X/Q-Orchestrate
/plugin install q-orchestrate@q-orchestrate- tashan score: 40.0
- Adoption: 1 repos
- Freshness: 95.0
- Evidence coverage: 59% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- GitHub stars: 0
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Q Orchestrate scores 40 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.
- The whole series behind any row, back to the first day we measured it
- The replacement, named — not just the news that something died
tashan doctorover your own config, on your own machine
Start a 7-day trial › Everything measured on this page stays free.
Show your score
source ↗ · plugin:darkri-x/q-orchestrate/q-orchestrate
Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.
Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.
Measured 2026-09-13 · scorer s5 · how · something wrong here?