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-memorygit 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-memory)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-memory"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-memory/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-memory"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-memory.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.00039 | $0.02898 |
| Opus 5.5 | $0.00016 | $0.01159 |
| Sonnet 5.5 | $0.00008 | $0.00580 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
mastermind-memory 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Memory
This skill is invoked with Skill("mastermind-memory"), for example by the mastermind router. (/mastermind:memory is a different command, a memory CLI quick reference that comes with the orgs pack: monomind packs add orgs.)
Inputs
brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)org_name: org whose memory to operate on (required)action: ingest | recall | query | update | forget | synthesize | decay | listtopic: topic or entity name (required for ingest/recall/update/forget)layer: knowledge | daily | tacit (default: knowledge)category: projects | areas | resources | archives (for layer=knowledge; default: resources)content: fact or note body (required for ingest/update)caller: command | master
Memory Architecture (PARA)
Three layers, mirrored to .monomind/orgs/<org_name>-memory/:
.monomind/orgs/<org>-memory/
knowledge/ ← Layer 1: PARA knowledge graph
projects/<topic>/
summary.md
items.yaml
areas/<topic>/
summary.md
items.yaml
resources/<topic>/
summary.md
items.yaml
archives/<topic>/
summary.md
items.yaml
index.md
daily/ ← Layer 2: Raw timeline (YYYY-MM-DD.md)
tacit.md ← Layer 3: Org operating patterns
PARA rules:
- projects — active work with a goal/deadline; archive when complete
- areas — ongoing responsibilities, no end date
- resources — reference material, topics of interest
- archives — inactive items from any category
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 Memory Root
memRoot=".monomind/orgs/${org_name}-memory"
mkdir -p "$memRoot/knowledge/projects" "$memRoot/knowledge/areas" \
"$memRoot/knowledge/resources" "$memRoot/knowledge/archives" \
"$memRoot/daily"
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 · 322 lines · 39 tokens per session scan A 18a67cd00d95
mastermind-memory 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 2,898 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-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
claude-compaction-restore
Use when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched.
retiring-and-inheriting-a-seat
Use when you are a sitting agent near your context threshold (85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure)…
llm-wiki
Build and maintain a persistent, interlinked Markdown knowledge base: ingest sources once, cross-reference and flag contradictions, answer questions from it, and check it for broken links and gaps.
session-compaction-and-restore
Use when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet…