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-monitorgit 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-monitor)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-monitor"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-monitor/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-monitor"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-monitor.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.00041 | $0.12698 |
| Opus 5.5 | $0.00016 | $0.05079 |
| Sonnet 5.5 | $0.00008 | $0.02540 |
| Haiku 4.5 | $0.00004 | $0.01270 |
Grade A, and why
mastermind-monitor 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 — 1,270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Monitor
Invoked via mastermind:monitor or /mastermind-monitor.
A monitor is a named, forever-running task executor. It polls one or more task sources on a configurable interval, claims matching tasks, hands them off to a Claude agent for execution, posts back results as comments/status updates, and self-reschedules via ScheduleWakeup.
CLI Flags
--action start | stop | pause | resume | status | list | add-source | tick
--name monitor name (slug, e.g. "dev-agent")
--source linear | github | monotask | filesystem
--interval poll interval in seconds (default: 120)
--user filter by assignee username/email (can be repeated)
--state filter by task state/status (can be repeated, default: open/todo)
--max-concurrent max tasks in flight (default: 1)
--agent agent type to execute tasks (default: coder)
--project monotask project/board name, or gh repo (org/repo)
--team Linear team ID or slug
--folder filesystem folder path to watch (for source=filesystem)
--label filter by label (can be repeated)
--caller command | master (internal — skip brain load if "command")
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 Monitor Config Directory
MONITOR_DIR=".monomind/monitor"
mkdir -p "$MONITOR_DIR"
Step 2 — Dispatch by Action
list (default when no --action)
echo "MONITORS"
echo "────────────────────────────────────────"
for f in "$MONITOR_DIR"/*.json; do
[ -f "$f" ] || continue
jq -r '
"[\(.name)] status=\(.status // "active") interval=\(.poll_interval)s agent=\(.agent_type)
sources: \([(.sources // [])[].type] | join(", "))
last_tick: \(.last_tick // "never") tasks_done: \(.stats.done // 0) tasks_failed: \(.stats.failed // 0)"
' "$f"
echo ""
done
start
Creates a new monitor config and triggers the first tick.
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 · 1,270 lines · 41 tokens per session scan A d4c53917e3c8
mastermind-monitor is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 12,698 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.