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 wiolett-industries/marketplace --skill using-agent-memorygit clone --depth 1 https://github.com/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/using-agent-memory)<a href="https://agentmods.dev/skills/wiolett-industries/marketplace/using-agent-memory"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/using-agent-memory.svg" alt="Measured on agentmods" 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.00064 | $0.01482 |
| Opus 5 | $0.00032 | $0.00741 |
| Sonnet 5 | $0.00013 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
using-agent-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Agent Memory
Agent Memory is the MCP-backed durable memory system. It is separate from Codex built-in memory, chat history, and .workflow/ artifacts. Use Codex built-in memory only as background; use Agent Memory MCP for durable repo facts and reusable workflows when its tools are available.
Retrieval Gate
At conversation start, after compaction, or before non-trivial repository work, decide whether durable knowledge can change the answer or execution path. Do not wait for the user to explicitly ask for memory.
- For non-trivial repository work, run one memory read after the repo root is known whenever prior decisions, conventions, failures, setup, architecture, or user preferences could affect the result.
- Use
memory_recapwhen the task needs broad recovery across several memories; usememory_queryfor a focused question; usememory_recallonly with a non-emptymemory_idalready returned by query/list/recap or named explicitly by the user. Never usememory_recallas the first semantic search or startup recall. - Query
globalonly when a cross-project user preference or stable work habit could matter. - Skip the MCP read only for self-contained facts, trivial formatting, translation, or work whose outcome cannot reasonably depend on durable context.
- Escalate to
memory_recall,memory_list, ormemory_inspectonly when the focused query identifies a relevant entry, the index appears stale, or memory health itself is under investigation.
Pass the absolute workspace_root for project reads and writes whenever server cwd may differ from the repo. When the user explicitly asks about another project or names its path, keep scope: project and pass that other project's absolute root to memory_query (focused) or memory_recap (broad); this reads only that project's store and never initializes it. Do not scan sibling projects or write to another root unless the user explicitly authorizes that operation. An empty project result is not proof that memory is absent until the root and index/deep view have been checked.
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.
- 4d ago Changed · +1 lines 920a474d6eb7
- 8d ago First seen · 59 lines · 64 tokens per session scan A 3ac2a4cac35e
using-agent-memory is a skill published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 1,482 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.