agentmods.dev

memory

memory is a skill for Claude Code, Codex from render-examples/nanobot-render. It costs 12 tokens per session (452 once invoked), scanned A, original, MIT.

A two-level memory setup that stores the agent’s style, user preferences, project facts, and past events in files.

In plain words
What is it for?
Remembering project details and user preferences, preserving long-term facts, and searching an append-only record of previous events.
Why use it?
It keeps useful context between conversations without loading the entire history every time. Search guidance helps find older events when needed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 5repo 3mo ago A scan 12 tokens original MIT

Good fit Remembering project details and user preferences, preserving long-term facts, and searching an append-only record of previous events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/render-examples/nanobot-render/memory
View source ↗ render-examples/nanobot-render nanobot-0iyy.onrender.com
Install

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.

Any agent
npx skills add render-examples/nanobot-render --skill memory
Clone the repo
git clone --depth 1 https://github.com/render-examples/nanobot-render

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/render-examples/nanobot-render/memory/github.svg)](https://agentmods.dev/skills/render-examples/nanobot-render/memory)
Your own site
<a href="https://agentmods.dev/skills/render-examples/nanobot-render/memory"><img src="https://agentmods.dev/badge/skills/render-examples/nanobot-render/memory/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.

agentmods 80×15 button for memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/render-examples/nanobot-render/memory"><img src="https://agentmods.dev/badge/skills/render-examples/nanobot-render/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 452 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00452
Opus 5.5 $0.00005 $0.00181
Sonnet 5.5 $0.00002 $0.00090
Haiku 4.5 $0.00001 $0.00045

Measured 1mo ago against content hash 2421337ad511, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

nanobot/skills/memory/SKILL.md · 37 lines

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-in grep tool 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 default files_with_matches mode before expanding to full content
  • Use output_mode="content" plus context_before / context_after when you need the exact matching lines
  • Use fixed_strings=true for literal timestamps or JSON fragments
  • Use head_limit / offset to page through long histories
  • Use exec only 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-log command.
Changes

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.

  1. 1mo ago First seen · 37 lines · 12 tokens per session scan A 2421337ad511

Subscribe to this mod's changes

memory is a skill published in the GitHub repository render-examples/nanobot-render (5 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 452 once invoked, about $0.0000 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-31.

ChatbotsLLMMemory and contextai-agentai-agentschatbotdocker
Related

Other skills, from other repositories

memory

Split memory system with USER.md for durable personal profile and MEMORY.md for token-budgeted operational context.

RikyZ90/ShibaClaw · 22 tokens

ai-skills

Use when building LLM applications, RAG knowledge bases, AI agents, terminal coding agents, multi-model orchestration, plugin-based agent harnesses, or file translation. Index of 14 skills: Dify, LangChain, LlamaIndex, Ollama, Transformers, Hermes Agent, OpenClaw, OpenCode, Pi, DocuTranslate, DeepSeek Harness and more.

znlgis/opengis-skills · 81 tokens

capacity-planning

Capacity trend analysis and projections: disk growth rates, resource consumption patterns, and time-to-exhaustion estimates. AUTO-CONSULT when: disk usage exceeds 60%, memory usage is consistently high, user asks about server capacity or growth trends, or during periodic maintenance reviews.

anatolykoptev/dozor · 59 tokens

memory

Knowledge base: store and retrieve operational knowledge. AUTO-CONSULT when: resolving an incident (search for similar past incidents first), after fixing a non-trivial issue (save the solution), during capacity reviews (check historical trends), or when user asks about past events.

anatolykoptev/dozor · 56 tokens

session-logs

Search and analyze your own session logs (older/parent conversations) using jq.

kaivyy/kabot · 20 tokens

mem0-vercel-ai-sdk

Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…

mem0ai/mem0 · 146 tokens