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.svg" alt="Measured on agentmods" 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.00061 | $0.01585 |
| Opus 5 | $0.00030 | $0.00792 |
| Sonnet 5 | $0.00012 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00159 |
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 8d 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 — 119 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, depending on your agent's tier. Use the search/recall tools PROACTIVELY -- do not wait to be asked. Only call a tool your agent's tools: frontmatter actually grants — see the tier table below and the mcp-tools skill for the full 13-tool inventory.
Tools Available
| Tool | Purpose | All agents | Write agents only | Notes agents only |
|---|---|---|---|---|
search_context |
Search ingested context chunks | Yes | -- | -- |
semantic_search |
Find memories by similarity query | Yes | -- | -- |
semantic_recall |
Get formatted memories for current context | Yes | -- | -- |
semantic_store |
Store a new memory with embedding | -- | Yes | -- |
store_note / read_note / list_notes |
Persist/read/list note documents | -- | -- | Yes |
trigger_ingest |
Queue one just-written document (corpus + relative_path) for immediate indexing (~3s to become searchable) instead of waiting up to 15 minutes |
-- | -- | Yes |
Write agents (search/recall/store): developer, architect, debugger, analyst, researcher, reviewer, optimizer.
Read-only agents: tech-writer, devops, gitops, mcp-builder, prompt-engineer.
Notes + trigger_ingest agents: architect, researcher only — trigger_ingest is deliberately withheld from the rest of the write tier because it's only useful paired with store_note (otherwise you're re-indexing a document you didn't write), and each call costs an LLM context-gen call.
trigger_ingest 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.
Uwaga: Jesli ten skill jest aktywny w repozytorium bez MCP server
memory, pomin te instrukcje. Agent bez dostepu domcp__memory__*toolow powinien po prostu pracowac bez pamieci semantycznej -- file-based fallback w.scaffolding/agent-memory/wciaz dziala.
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.
- 8d 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 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,585 once invoked, about $0.0003 per session on Opus 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
turnstile-brain-init
Opt-in bulk bootstrap of turnstile/code/ -- one linked note per source file. The default pipeline is lazy (code notes only for ticket-touched files, written when the ticket passes review); this is the eager exception. Dispatched by /turnstile:brain-init only.
turnstile-brain
Vault layout, the shared note format, and the check-the-brain-first mandate. Auto-loads whenever any turnstile skill starts new work or /turnstile:review is about to commit.
turnstile-remember
Files a user-dictated note into the vault via brain-curator -- the user authors the content, the curator only files, tags, and links it. Dispatched by /turnstile:remember or conversate routing only; available in both capture modes.
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
memory-curator
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…