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 memory-toolkitgit 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/memory-toolkit)<a href="https://agentmods.dev/skills/monoes/monomind/memory-toolkit"><img src="https://agentmods.dev/badge/skills/monoes/monomind/memory-toolkit/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/memory-toolkit"><img src="https://agentmods.dev/badge/skills/monoes/monomind/memory-toolkit.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.00045 | $0.00653 |
| Opus 5.5 | $0.00018 | $0.00261 |
| Sonnet 5.5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
memory-toolkit 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Toolkit
Monomind ships a persistent, namespaced memory store backed by local SQLite (sql.js/WASM) with local HF embeddings; keyword search is the fallback when embeddings aren't available. Use it to avoid re-solving the same problem twice across sessions.
Before starting non-trivial work
Search for prior art first:
npx monomind memory search --query "[task keywords]" --namespace patterns
npx monomind memory search --query "[task keywords]" --namespace solutions
Store data
# REQUIRED: --key and --value. OPTIONAL: --namespace (default: "default"), --ttl, --tags
npx monomind memory store --key "pattern-auth" --value "JWT with refresh tokens" --namespace patterns
npx monomind memory store --key "bug-fix-123" --value "Fixed null check in parser" --namespace solutions --tags "bugfix,auth"
Search data (semantic / keyword / hybrid)
# REQUIRED: --query. OPTIONAL: --namespace, --limit, --threshold, --type
npx monomind memory search --query "authentication patterns"
npx monomind memory search --query "JWT" --type keyword
npx monomind memory search --query "error handling" --namespace patterns --limit 5
| Search type | Description | Best for |
|---|---|---|
semantic |
Vector similarity search | Concept / meaning matching |
keyword |
BM25 full-text search | Exact term matching |
hybrid |
Combined semantic + keyword | General purpose (default) |
--build-hnsw is a dead fallback: it's a no-op unless the SQLite bridge is
down and the sql.js WASM path is in use. Normal searches don't need it.
List and retrieve
npx monomind memory list --namespace patterns --limit 10
npx monomind memory retrieve --key "pattern-auth" --namespace patterns
MCP equivalents
mcp__monomind__memory_pattern-store({ key: "pattern-auth", value: "...", namespace: "patterns" })
mcp__monomind__memory_pattern-search({ query: "authentication patterns", namespace: "default", limit: 10, threshold: 0.7, type: "hybrid" })
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 · 71 lines · 45 tokens per session scan A 1da2bb13d681
memory-toolkit is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 653 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…