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 komluk/scaffolding --skill semantic-memory-mcpgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/semantic-memory-mcp)<a href="https://agentmods.dev/skills/komluk/scaffolding/semantic-memory-mcp"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/semantic-memory-mcp/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/komluk/scaffolding/semantic-memory-mcp"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/semantic-memory-mcp.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.00079 | $0.01935 |
| Opus 5.5 | $0.00032 | $0.00774 |
| Sonnet 5.5 | $0.00016 | $0.00387 |
| Haiku 4.5 | $0.00008 | $0.00194 |
Grade A, and why
semantic-memory-mcp 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 7d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Memory MCP Usage
You have access to a subset of the 13 memory MCP tools. Use the search/recall tools PROACTIVELY -- do not wait to be asked. Only call a tool your agent's tools: frontmatter actually grants; that frontmatter is authoritative. See the mcp-tools skill for the full 13-tool inventory and access table.
Tools Available
| Tool | Purpose |
|---|---|
search_context |
Search ingested context chunks |
semantic_search |
Find memories by similarity query |
semantic_recall |
Get formatted memories for current context |
semantic_store |
Store a new memory with embedding |
store_note / read_note / list_notes |
Persist/read/list note documents |
trigger_ingest |
Queue one just-written document (corpus + relative_path) for immediate indexing (~3s to become searchable) instead of waiting up to 15 minutes |
trigger_ingest is only useful paired with store_note (otherwise you are re-indexing a document you didn't write), and each call costs an LLM context-gen call. It is path-scoped to a single document -- it cannot trigger a full backfill -- and it is fire-and-forget: it returns once the document is queued, not once indexing completes. Don't expect a synchronous "done" result; the document becomes searchable a few seconds later.
Note: If this skill is active in a repository without the
memoryMCP server, skip these instructions. An agent withoutmcp__memory__*tools should simply work without semantic memory -- the file-based fallback in.scaffolding/agent-memory/(see theagent-memoryskill) keeps working. Never block on missing infrastructure.
Automatic Baseline
Baseline recall and store already happen without you:
- Recall: injected at prompt/task start by the
memory-recall.shhook (interactive,<recalled-memories>) or the platformMEMORY_AUTO_RECALL(## Relevant project memory). - Store: the memory-ingest Stop hook runs
distilland auto-stores high-confidence candidates; the platformMEMORY_AUTO_STOREstores the 1-3 bullets of your final## Remembersection. Apply the same Quality Gate below to those bullets.
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.
- 7d ago Changed · +26 lines · +18 tokens per session 510d578f4ee8
- 1mo ago First seen · 119 lines · 61 tokens per session scan A d1b22ee159ce
semantic-memory-mcp is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,935 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.
use
Connect or switch Codex to a local NeatContext Context by name or list number. Use only when the user explicitly invokes this skill, names a context to connect, or agrees to a routing suggestion.
delete
Preview and permanently delete a NeatContext context while preserving any externally linked knowledge folder. Use only when the user explicitly invokes this skill or clearly asks to delete a context.