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-org-settingsgit 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-org-settings)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-org-settings"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-org-settings/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-org-settings"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-org-settings.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.00040 | $0.03536 |
| Opus 5.5 | $0.00016 | $0.01414 |
| Sonnet 5.5 | $0.00008 | $0.00707 |
| Haiku 4.5 | $0.00004 | $0.00354 |
Grade A, and why
mastermind-org-settings 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 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.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Org Settings
This skill is invoked directly via /mastermind-org-settings.
It edits .monomind/orgs/<org_name>.json in place, and only ever touches fields that OrgDefSchema (packages/@monomind/cli/src/orgrt/types.ts) actually defines — every field listed below is read by the daemon (org.ts/daemon.ts/session.ts) at monomind org run/serve time. Its primary edit flow targets these fields only: name, goal, schedule, and run_config (budget_tokens, memory_namespace, max_turns_per_message). Role edits are not yet supported by this skill's edit action — roles is shown read-only via show.
There is no topology, governance, alert_threshold, or ceo_adapter in the org config — those are legacy fields with no runtime effect and are not part of this skill's edit surface. If an org's config file still carries them (the legacy format), convert it with monomind org migrate <name> first.
Inputs
brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)org_name: org to configure (required)action: show | edit | export | importfield: field to edit (name, goal, schedule, budget_tokens, memory_namespace, max_turns_per_message)value: new value for the fieldexport_path: path to write exported JSON (default:.monomind/exports/<org_name>-<timestamp>.json)import_path: path to JSON file to import fromcaller: command | master
Step 0 — Brain Load (standalone only)
If caller is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: ops.
Step 1 — Resolve Org
orgFile=".monomind/orgs/${org_name}.json"
[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found. Run /mastermind:createorg first."; exit 1; }
Step 2 — Execute Action
show (default)
Display current org config in a readable format:
echo "ORG SETTINGS — ${org_name}"
echo "──────────────────────────────────────────"
jq -r '
" Name: \(.name // "-")",
" Goal: \(.goal // "-")",
" Status: \(.status // "stopped")",
" Schedule: \(.schedule // "manual (no auto-schedule)")",
" Budget: \(.run_config.budget_tokens // 1000000) tokens",
" Memory namespace: \(.run_config.memory_namespace // ("org:" + (.name // "-")))",
" Max turns/message: \(.run_config.max_turns_per_message // 30)",
" Roles: \(.roles | length) agents"
' "$orgFile"
echo ""
echo " Run /mastermind-org-settings --org ${org_name} --action edit --field <field> --value <value>"
echo " Fields: name | goal | schedule | budget_tokens | memory_namespace | max_turns_per_message"
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 · 268 lines · 40 tokens per session scan A 234b49e1dfeb
mastermind-org-settings is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 3,536 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other skills, from other repositories
agent-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…
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.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.