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 agentmods add skills/render-examples/nanobot-render/memorynpx skills add render-examples/nanobot-render --skill memorygit clone --depth 1 https://github.com/render-examples/nanobot-renderWhat 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 | $0.00012 | $0.00452 |
| Opus 5 | $0.00006 | $0.00226 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
memory 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.
What it actually says
Memory
Structure
SOUL.md— Bot personality and communication style. Managed by Dream. Do NOT edit.USER.md— User profile and preferences. Managed by Dream. Do NOT edit.memory/MEMORY.md— Long-term facts (project context, important events). Managed by Dream. Do NOT edit.memory/history.jsonl— append-only JSONL, not loaded into context. Prefer the built-ingreptool to search it.
Search Past Events
memory/history.jsonl is JSONL format — each line is a JSON object with cursor, timestamp, content.
- For broad searches, start with
grep(..., path="memory", glob="*.jsonl", output_mode="count")or the defaultfiles_with_matchesmode before expanding to full content - Use
output_mode="content"pluscontext_before/context_afterwhen you need the exact matching lines - Use
fixed_strings=truefor literal timestamps or JSON fragments - Use
head_limit/offsetto page through long histories - Use
execonly as a last-resort fallback when the built-in search cannot express what you need
Examples (replace keyword):
grep(pattern="keyword", path="memory/history.jsonl", case_insensitive=true)grep(pattern="2026-04-02 10:00", path="memory/history.jsonl", fixed_strings=true)grep(pattern="keyword", path="memory", glob="*.jsonl", output_mode="count", case_insensitive=true)grep(pattern="oauth|token", path="memory", glob="*.jsonl", output_mode="content", case_insensitive=true)
Important
- Do NOT edit SOUL.md, USER.md, or MEMORY.md. They are automatically managed by Dream.
- If you notice outdated information, it will be corrected when Dream runs next.
- Users can view Dream's activity with the
/dream-logcommand.
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 · 37 lines · 12 tokens per session scan A 2421337ad511
memory is a skill published in the GitHub repository render-examples/nanobot-render (5 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 452 once invoked, about $0.0001 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-31.
Other skills, from other repositories
lumina-backend-api
Implement and debug the Express and TypeScript backend for Lumina. Use when editing files under server/src or server/package.json, changing authentication, conversations, guest flows, chat routes, models, middleware, API contracts, or Gemini and Pinecone service wiring outside the dedicated knowledge-ingestion…
lumina-frontend-ui
Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or frontend API wiring.
lumina-mcp-server
Develop and maintain the standalone Lumina MCP server. Use when editing files under mcpserver/, adding or modifying tools, resources, prompts, middleware, configuration, or transport behavior for the Model Context Protocol server.
lumina-rag-knowledge
Manage Lumina's retrieval-augmented generation and knowledge ingestion workflow. Use when editing server/src/services/knowledgeBase.ts, server/src/services/pineconeClient.ts, server/src/scripts/knowledgeCli.ts, server/src/models/KnowledgeSource.ts, files under server/knowledge, manifest-based sync inputs, or debugging…
lumina-agentic-mcp
Work on the Python multi-agent pipeline and MCP client in agenticai. Use when editing files under agenticai/, changing agent orchestration, configuration loading, MCP client connectivity, async execution flow, pipeline startup commands, or cloud deployment wrappers for the Python service.
lumina-infra-deploy
Work on Lumina deployment and infrastructure assets. Use when editing terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, ADVANCEDDEPLOYMENTS.md, agenticai/deployments/, or other files related to Docker, Terraform, AWS or Azure rollout behavior, environment wiring, and release automation.