U Ministry Utility
0“No ministry functionality in pack; README describes a developer tool: 'Define your agent team in YAML, boot it with one command. Claude…”
source unavailable
mvschwarz/openrig
Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work.
Trust Score
30.5
Last full review 2026-09-27 · Trust Score decays −2 points per month without a fresh review (never below 20)
security cap applied — score capped at 45U Ministry Utility
0“No ministry functionality in pack; README describes a developer tool: 'Define your agent team in YAML, boot it with one command. Claude…”
source unavailable
M Maturity
50“api.releases: 'latest tag v0.6.4 published 2026-10-02T05:45:35Z'; latest_commit dated 2026-10-02 (same day as pack fetch). npm badge in…”
source unavailable
32.5 → 32.5 (+0.0 over window)
ranked #6 of 7 in G7
mvschwarz/openrig looks like a candidate for cli & developer tools; Candidate hint 'none' upheld: pure developer/AI-agent tooling (G7 CLI), no ministry lane applies even generously; U=0 'no signal' for ministry fit.
Use it with
Selected: Gloo AI Studio
Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.
Step 1 — Connect Refinry once (prompt only)
Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.
https://studio.ai.gloo.com/I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate mvschwarz/openrig: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Some clients need manual setup. Follow the plain-language steps on the Docs page.
Step 2 — Plan your first step
Tell the AI what you want to do; edit this to match your situation.
I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of mvschwarz/openrig (https://refinry.dev) and help me assess it for using mvschwarz/openrig for cli & developer tools in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.
S Security / License
25license 75 · security 25
“api.repos.license.spdx_id: 'Apache-2.0' (permissive; dep scan unfetched -> 75). Security: 'unfetched: SECURITY.md/dependabot/CodeQL/OSV not…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“Developer: 'npm install -g @openrig/cli' + 'Requires Node.js 22 or 24 and tmux' + 'rig setup --dry-run' (README) = clear install docs and…”
source unavailable
C Community Trust
25“api.repos: 'stargazers_count': 3975, 'forks_count': 263, Q&A discussion link 'github.com/mvschwarz/openrig/discussions/92' (README) — real…”
source unavailable
I AI-Agent Integrability
75“README: accurate install/use sections ('Install and first run', getting-started guide), npm package '@openrig/cli' manifest metadata…”
source unavailable