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.
git 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/commands/monoes/monomind/understand)<a href="https://agentmods.dev/commands/monoes/monomind/understand"><img src="https://agentmods.dev/badge/commands/monoes/monomind/understand/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/commands/monoes/monomind/understand"><img src="https://agentmods.dev/badge/commands/monoes/monomind/understand.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.00032 | $0.01361 |
| Opus 5.5 | $0.00013 | $0.00544 |
| Sonnet 5.5 | $0.00006 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
understand 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 yesterday.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mastermind:understand — Semantic Enrichment
Enriches the current project's monograph knowledge graph with summaries, architectural layers, and semantic relationships.
Designed to run inside Claude Code — uses YOUR current session for LLM work via
the Task tool. No ANTHROPIC_API_KEY required. The script handles layer detection
and DB writes; you (Claude) handle per-file summarization.
Parse Arguments
Parse $ARGUMENTS for these flags:
--dir <path>— project directory (default: cwd)--db <path>— monograph.db path (default:<dir>/.monomind/monograph.db)--full— force full re-analysis--no-llm— heuristic-only mode (no per-file summaries)--layers-only— skip per-file analysis, only re-detect layers--max-files <N>— stop after N files (0 = all)--dry-run— show what would happen, don't write
Bare path argument → --dir.
Step 1: Locate project, DB, and script
DIR="${ARGUMENTS_dir:-$(pwd)}"
DB="${ARGUMENTS_db:-$DIR/.monomind/monograph.db}"
# Find understand-analyze.mjs (ships with monomind globally)
GLOBAL_ROOT=$(npm root -g 2>/dev/null)
SCRIPT="$GLOBAL_ROOT/monomind/packages/@monomind/cli/scripts/understand-analyze.mjs"
[ ! -f "$SCRIPT" ] && SCRIPT="$GLOBAL_ROOT/@monoes/monomindcli/scripts/understand-analyze.mjs"
If $DB does not exist:
monograph.db not found at
$DB. Build it first:npx monomind monograph build
If $SCRIPT does not exist:
understand engine missing. Update:
npm install -g monomind@latest
In either case, STOP.
Step 2: Run the script in heuristic mode (always — fast and deterministic)
This step is non-negotiable. The script handles:
- File node discovery from monograph.db
- Heuristic layer detection from file paths
- DB writes (community_id + properties)
- graph.json emission to
.understand/knowledge-graph.json - Auto-shadowing the DB to
/tmpwhen it lives on a network FS
node "$SCRIPT" --dir "$DIR" --db "$DB" --no-llm
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.
- yesterday First seen · 139 lines · 32 tokens per session scan A a7243afe6a06
understand is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 1,361 once invoked, about $0.0001 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 commands, from other repositories
claude-flow-memory
Interact with Claude-Flow memory system.
sessions
Manage OpenAI Codex session history, aliases, and session metadata.
checkpoint
Create an identified recovery point and inspect exact restoration differences.
recall
Retrieve scoped lessons and evaluate their assumptions, conflicts, and applicability.
retro
Write this session's lessons into the project's lessons/ directory using the memory-discipline format.
save-session
Save current session state to a dated file in /.codex/session-data/ so work can be resumed in a future session with full context.