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/yujiachen-y/agent-bundle/update-memorynpx skills add yujiachen-y/agent-bundle --skill update-memorygit clone --depth 1 https://github.com/yujiachen-y/agent-bundleWrote 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/yujiachen-y/agent-bundle/update-memory)<a href="https://agentmods.dev/skills/yujiachen-y/agent-bundle/update-memory"><img src="https://agentmods.dev/badge/skills/yujiachen-y/agent-bundle/update-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 | $0.00014 | $0.00164 |
| Opus 5 | $0.00007 | $0.00082 |
| Sonnet 5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
update-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.
What it actually says
Update Memory
When the user provides a new event or preference update:
- Read the existing profile with
mcp__fs__read_filefrom/memory/<userId>.json. - Merge the new event details into the existing profile object.
- Write the merged profile with
mcp__fs__write_fileto/memory/<userId>.json. - Return a brief confirmation describing what was updated.
Rules:
- Never overwrite unrelated fields with empty values.
- Preserve existing profile keys unless the user explicitly changes them.
- If the profile file does not exist, create a new one with the event data.
- Always include an
updatedAtISO timestamp in the profile.
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 First seen · 21 lines · 14 tokens per session scan A b21706686e48
update-memory is a skill published in the GitHub repository yujiachen-y/agent-bundle (10 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 164 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
store_decision
Store a decision to episodic memory for future recall.
search_past_decisions
Search for similar past decisions using hybrid search.
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-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…
stats
Displays memory usage statistics for the current session and project including counts by category, age distribution, and API latency. Use when checking how many memories exist, reviewing session activity, or auditing memory distribution across categories.
peek
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if a decision was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.