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 RikyZ90/ShibaClaw --skill memorygit clone --depth 1 https://github.com/RikyZ90/ShibaClawWrote 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/rikyz90/shibaclaw/memory)<a href="https://agentmods.dev/skills/rikyz90/shibaclaw/memory"><img src="https://agentmods.dev/badge/skills/rikyz90/shibaclaw/memory.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00468 |
| Opus 5 | $0.00011 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 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.
What it actually says
Memory
Structure
USER.md— Durable personal profile and preferences. Not token-compacted; keep it focused on long-lived user facts.memory/MEMORY.md— Operational long-term facts. Injected into every system prompt under# Memory, truncated from the bottom if it exceeds the token budget (~2000 tokens default).memory/HISTORY.md— Append-only log with[YYYY-MM-DD HH:MM] [#tag1 #tag2]entries. Never injected. Search it withmemory_searchor grep when historical context is missing.
MEMORY.md Layout
Sections are ordered by survival priority — top sections persist under truncation, bottom sections are dropped first.
## Environment— OS, runtime, tooling constraints, local services, provider setup## Entities— people, projects, repos, services referenced often## Project State— milestones, blockers, medium-term status, important decisions## Dynamic Context— current tasks, recent decisions, in-progress work
Rules:
- One fact per bullet, no prose paragraphs
- Update/replace existing facts instead of appending duplicates
- Put personal profile and preferences in
USER.md, not inmemory/MEMORY.md - Put durable operational facts in the top three MEMORY sections; only transient state goes in Dynamic Context
- Keep the file concise — the system auto-compacts when it exceeds ~1600 tokens
Missing Context
If a topic feels incomplete, search HISTORY.md first before assuming a fact was never recorded. Use the memory_search tool for semantic queries, or grep for exact matches:
grep -i "keyword" memory/HISTORY.md
Proactive Context Retrieval
If the user refers to past discussions or ongoing workflows you don't recall: search HISTORY.md before responding.
Auto-consolidation
Handled automatically every ~10 messages. Long-term memory is auto-compacted by the system when it grows beyond the configured threshold.
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 · 45 lines · 22 tokens per session scan A 18a8560190cf
memory is a skill published in the GitHub repository RikyZ90/ShibaClaw (80 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 468 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-30.
Other skills, from other repositories
memory-triage
Persistent long-term memory protocol powered by mem0. Evaluate conversations for durable facts worth storing via memoryadd. Handles identity, preferences, decisions, configurations, rules, projects, and relationships. Loaded by the openclaw-mem0 plugin when skills mode is active.
mem0-dream
Consolidates stored memories by merging duplicates, resolving contradictions, and pruning stale entries. Use when memory count is high, search results feel noisy or repetitive, or periodic cleanup is needed to maintain memory quality.
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0
Mem0 SDK reference covering Python and TypeScript APIs, memory client methods, configuration, and framework integrations. Use when writing code that calls mem0 APIs, configuring memory providers, or integrating mem0 into an application.
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…