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 ambient-code/platform --skill memorygit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/memory)<a href="https://agentmods.dev/skills/ambient-code/platform/memory"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/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.
<a href="https://agentmods.dev/skills/ambient-code/platform/memory"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/memory.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.00957 |
| Opus 5.5 | $0.00040 | $0.00383 |
| Sonnet 5.5 | $0.00020 | $0.00191 |
| Haiku 4.5 | $0.00010 | $0.00096 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- memory — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management
Manage the auto-memory system for the Ambient Code Platform project.
Usage
/memory # Show summary of all memories
/memory search <query> # Search for a topic
/memory audit # Check for stale/duplicate memories
/memory prune # Remove stale memories (with confirmation)
/memory add <topic> # Create a new memory
User Input
$ARGUMENTS
Parse the subcommand from $ARGUMENTS. Default to summary if empty.
Memory Location
All memory files live at:
$HOME/.claude/projects/<project-slug>/memory/
Use the active project's slug (the repo path with / replaced by -).
The index file is MEMORY.md in that directory.
Subcommands
/memory — Summary
- Read
MEMORY.mdto get the index - Count total memories by type (user, feedback, project, reference)
- List the most recently modified files
- Report: total count, breakdown by type, last modified dates
/memory search <query>
- Read
MEMORY.mdfor the index - Grep through all memory files for the query term
- Read matching files and show relevant excerpts
- Report: matching files with frontmatter (name, type, description)
/memory audit
Check for quality issues:
- Stale memories — project/reference memories older than 3 months may be outdated
- Duplicate memories — similar names or descriptions across files
- Missing frontmatter — files without proper
name,description,typefields - Orphaned files — memory files not referenced in
MEMORY.md - Broken links —
MEMORY.mdentries pointing to nonexistent files - Oversized index —
MEMORY.mdapproaching the 200-line truncation limit
Report each issue with the file path and suggested action.
/memory prune
- Run the audit checks
- Present findings to the user
- For each stale/duplicate/orphaned memory, ask: keep, update, or delete?
- Execute confirmed deletions
- Update
MEMORY.mdindex accordingly
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 129 lines · 99 tokens per session scan A a2fd9bd480ae
memory is a skill published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 957 once invoked, about $0.0004 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-30.
Other skills, from other repositories
kb-builder
Build an Obsidian-compatible knowledge base from public web sources using the TinyFish CLI. Use this skill when a user wants a builder-grade markdown knowledge base on a technical topic, asks for a structured research vault, or wants a topic compiled from live public sources into interlinked markdown files. Supports…
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
weknora-rag-search
Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.
powercontext-project-context
A project-memory guide for searching, saving, correcting, and transferring durable context through the PowerContext service. It distinguishes ordinary conversation from information that should persist between sessions.
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.