mastermind-approval-detail

mastermind-approval-detail is a skill for Claude Code, Codex from monoes/monomind. It costs 39 tokens per session (1,133 once invoked), scanned A, original, Apache-2.0.

A tool for viewing and resolving approval requests made by agents. An approval request is a pause where an agent asks a person to allow a restricted action such as running commands or accessing the web.

In plain words
What is it for?
Use it to list, inspect, approve, or deny individual requests from agents.
Why use it?
It gives a human a clear queue for checking what an agent wants to do before allowing or rejecting it. Decisions are delivered to a running organisation when possible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to list, inspect, approve, or deny individual requests from agents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monoes/monomind/mastermind-approval-detail
Install

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.

Any agent
npx skills add monoes/monomind --skill mastermind-approval-detail
Clone the repo
git clone --depth 1 https://github.com/monoes/monomind

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mastermind-approval-detail

README.md
[![agentmods](https://agentmods.dev/badge/skills/monoes/monomind/mastermind-approval-detail/github.svg)](https://agentmods.dev/skills/monoes/monomind/mastermind-approval-detail)
Your own site
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-approval-detail"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-approval-detail/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.

agentmods 80×15 button for mastermind-approval-detail

Your own site · 80×15
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-approval-detail"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-approval-detail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,133 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.01133
Opus 5.5 $0.00016 $0.00453
Sonnet 5.5 $0.00008 $0.00227
Haiku 4.5 $0.00004 $0.00113

Measured 2d ago against content hash a1dd740dbc9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mastermind-approval-detail 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.

.agents/skills/mastermind-approval-detail/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mastermind Approval Detail

This skill is invoked directly via /mastermind-approval-detail.


Inputs

  • brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
  • org_name: org the approval belongs to (required)
  • approval_id: approval request id (apr-…) or short prefix (required for show/approve/deny)
  • action: list | show | approve | deny
  • resolver: name recorded as resolvedBy (optional; the CLI defaults to human)
  • caller: command | master

The approval queue is .monomind/orgs/<org>/approvals.json, written by the Org Runtime when an agent asks to use a gated tool (Bash, WebFetch, WebSearch, org_complete). Always read and resolve it through the CLI: monomind org approve/deny deliver the decision to a running org's daemon (the waiting agent is notified at once) and fall back to updating the file when the org is not running.


Approval Record

Field Meaning
requestId Request id (apr-…); may be null on entries recorded before ids existed
roleId Role that asked
action Tool or action requested (e.g. Bash)
question What the agent asked
input Tool input the agent wants to run (may be null)
approved null = pending, true = approved, false = denied
ts / resolvedAt Request / resolution time (epoch ms)
resolvedBy Who resolved it

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 — Load Approval

orgFile=".monomind/orgs/${org_name}.json"
[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }

all=$(monomind org approvals "$org_name" --all --format json) || { echo "ERROR: Cannot read approvals for org '${org_name}'."; exit 1; }

if [ -n "$approval_id" ]; then
  approvalDef=$(echo "$all" | jq -c --arg id "$approval_id" \
    '[.items[] | select(.requestId != null and (.requestId == $id or (.requestId | startswith($id))))][0] // empty')
  [ -z "$approvalDef" ] && { echo "ERROR: Approval '${approval_id}' not found."; exit 1; }
  approvalId=$(echo "$approvalDef" | jq -r '.requestId')
  roleId=$(echo "$approvalDef" | jq -r '.roleId')
  approvalAction=$(echo "$approvalDef" | jq -r '.action')
fi

Read the full file on GitHub · 139 lines

Changes

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.

  1. 2d ago First seen · 139 lines · 39 tokens per session scan A a1dd740dbc9c

Subscribe to this mod's changes

mastermind-approval-detail is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,133 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.

Related

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.

ruvnet/metaharness · 66 tokens

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…

ruvnet/metaharness · 89 tokens

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.

ruvnet/metaharness · 85 tokens

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…

ruvnet/metaharness · 90 tokens

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.

ruvnet/metaharness · 79 tokens

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.

ruvnet/metaharness · 73 tokens