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 surrealdb/agent-skills --skill surrealdb-agent-memory-docsgit clone --depth 1 https://github.com/surrealdb/agent-skillsWrote 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/surrealdb/agent-skills/surrealdb-agent-memory-docs)<a href="https://agentmods.dev/skills/surrealdb/agent-skills/surrealdb-agent-memory-docs"><img src="https://agentmods.dev/badge/skills/surrealdb/agent-skills/surrealdb-agent-memory-docs/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/surrealdb/agent-skills/surrealdb-agent-memory-docs"><img src="https://agentmods.dev/badge/skills/surrealdb/agent-skills/surrealdb-agent-memory-docs.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.00085 | $0.01237 |
| Opus 5.5 | $0.00034 | $0.00495 |
| Sonnet 5.5 | $0.00017 | $0.00247 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade A, and why
surrealdb-agent-memory-docs scanned grade A with 1 finding 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 17d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: WebFetch(domain:surrealdb.com), Bash(curl -s https://surrealdb.com/*), Bash(ssh surrealdb.sh *) How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SurrealDB Agent Memory Documentation
Fetch the official SurrealDB Agent Memory docs, published at surrealdb.com/docs/agent-memory. Every page is available as markdown over HTTPS.
Naming
Agent Memory was developed as Spectron, and the rename is only partly done. Some pages still say "Spectron", so search for both names.
- Renamed: the
agent-memoryCLI and MCP server, and the SDKs (@surrealdb/memory,surrealdb-memory, …) - Unchanged:
SPECTRON_*env vars,X-Spectron-*headers, and the~/.config/spectron/config directory
Start here
https://surrealdb.com/docs/agent-memory/reference/agents.md: a condensed guide written for coding agentshttps://surrealdb.com/docs/agent-memory.md: the hub, which links every section
Section map
All paths are relative to https://surrealdb.com/docs/agent-memory/. Append .md.
| Path | Use for |
|---|---|
welcome/, quickstarts/ |
What it is; hosted, SurrealDB Cloud, and embedded setup |
architecture/, mental-model/ |
Principles, tri-temporal model, contexts and scope, sessions, categories, provenance |
memory-and-knowledge (hub) |
Index of the sections below |
ingest/authoritative/, ingest/experiential/ |
Uploading documents, bulk import, knowledge nodes, multimodal content, remember |
sessions/ |
Creating sessions, adding turns, chat sessions, state and diffs |
retrieve/ |
recall, hybrid search, BM25, graph traversal |
reasoning/ |
Extraction, reconciliation and supersession, authority, temporal validity |
operations/, tuning/ |
reflect, forget, profiles; models per stage, caching, ontology |
integrations/ |
sdks/, mcp-server/ (per coding assistant), frameworks/, ai-sdks/, surfaces/ (REST, embedded, filesystem view), voice, automation, observability |
cookbooks/ |
build/ end-to-end agents, migrate/ (from mem0, Zep, LangMem, vector stores), patterns/ |
reference/ |
REST and management API, SDK methods, MCP tools, CLI, configuration, data model, errors |
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.
- 17d ago First seen · 89 lines · 85 tokens per session scan A cbadb13cf103
surrealdb-agent-memory-docs is a skill published in the GitHub repository surrealdb/agent-skills (28 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 1,237 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-30.
Other skills, from other repositories
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, resolving TinyBase import paths, configuring browser or database…
tanstack-ai-memory-redis
Use when wiring redis() from @tanstack/ai-memory/redis in production — covers client setup (ioredis or node-redis via fromNodeRedis), the storage model, client-side ranking limits, and troubleshooting.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
omnigraph
Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…
api-reference
Memoria REST API endpoints, request/response formats, auth, rate limits. Use when calling or implementing API endpoints.
architecture
Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.