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 skills add monoes/monomind --skill mastermind-runorggit clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/mastermind-runorg)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-runorg"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-runorg/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/monoes/monomind/mastermind-runorg"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-runorg.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.00036 | $0.00872 |
| Opus 5.5 | $0.00014 | $0.00349 |
| Sonnet 5.5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
mastermind-runorg scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
no curl emissions, no delivery gaps. How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Runorg
Starts orgs through the Org Runtime SDK daemon. Every role becomes a live SDK session; events reach the dashboard through the daemon's own forwarder — no curl emissions, no delivery gaps.
Steps
- Resolve the org.
org_namefrom params. List available orgs when missing:monomind org list. - Detect the legacy config format. Do NOT rely on
monomind org validateto catch legacy-format config files — one with no structural violations (unique role ids, one root, resolvablereports_to, parseable schedule) passes schema validation even though it still carries legacy fields. Detect them directly:jq 'has("topology") or has("board_id") or has("loop") or ([.roles[]? | has("agent_type")] | any)' .monomind/orgs/<name>.jsontrue→ step 3 (migrate first).false→ step 4 (validate as-is).
- Migrate (legacy-format configs).
monomind org migrate <name>rewrites the file in the current format — the original is kept as<name>.v1.json. In confirm mode ask first; in auto mode migrate and state it. If migration fails, stop and surface the error. - Validate. Run
monomind org validate <name>on the config (post-migration if step 3 ran).- Valid → step 5.
- Invalid → surface the validator output and stop.
- Estimate scope and budget. Before starting, read the numbers already sitting in
the org config and print a short summary — this is a read-and-summarize step, not a
spend prediction, so the user sees scope and the configured ceiling before any agent-hour
is spent, not only after the run stops on a budget:
Print this summary unconditionally (auto and confirm mode alike) before step 6.orgFile=".monomind/orgs/<name>.json" roleCount=$(jq '.roles | length' "$orgFile") maxConcurrent=$(jq -r '.run_config.max_concurrent_agents // 4' "$orgFile") orgBudgetTokens=$(jq -r '.run_config.budget_tokens // 1000000' "$orgFile") roleBudgets=$(jq -r '.roles[] | " - \(.id): budget_tokens=\(.budget_tokens // "org-default split"), budget_usd=\(.budget_usd // "none")"' "$orgFile") echo "About to run ${roleCount} role(s) (max ${maxConcurrent} concurrent)." echo "Org-wide token budget ceiling: ${orgBudgetTokens}" echo "Per-role overrides:" echo "${roleBudgets}" - Start.
- One-shot (no
schedulein config): run in background bash:monomind org run <name> --task "<optional task from params>" - Scheduled (
scheduleset): ensure the daemon host is up:monomind org serve(background) — it picks up every scheduled org.
- One-shot (no
- Confirm liveness. Within ~15 s:
monomind org status <name>showsrunning. Surface the dashboard link (<CTRL_URL>/orgs) andmonomind org logs <name> --followas the tail command. - Never spawn a boss Task agent, create monotask boards, or emit dashboard events manually. The org daemon is the only way an org runs.
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.
- 2d ago First seen · 63 lines · 36 tokens per session scan A 474ff1b1665f
mastermind-runorg is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 872 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.
Other skills, from other repositories
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.