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/day1labs/openava/memory-maintenancenpx skills add Day1Labs/OpenAva --skill memory-maintenancegit clone --depth 1 https://github.com/Day1Labs/OpenAvaWrote 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/day1labs/openava/memory-maintenance)<a href="https://agentmods.dev/skills/day1labs/openava/memory-maintenance"><img src="https://agentmods.dev/badge/skills/day1labs/openava/memory-maintenance.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.00020 | $0.00259 |
| Opus 5 | $0.00010 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
memory-maintenance 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
Memory Maintenance
Use this skill when the task is specifically about cleaning up, curating, or consolidating memory.
Retrieval Rules
- Start with
memory_recallto inspect relevant durable memory topics. - Use
memory_transcript_searchonly when exact past conversation details or timelines matter.
Update Rules
- Save durable facts only when confidence is high.
- Use
memory_upsertto create or update typed durable memories. - Use
memory_forgetwhen a memory is stale, superseded, or incorrect. - Prefer updating an existing topic over creating duplicates.
- Reserve
memory_transcript_searchfor recall, not as a write path.
Workflow
- Inspect the current durable memory state with
memory_recall. - Separate durable facts from transient notes.
- Update or create typed memory topics with
memory_upsert. - Remove obsolete topics with
memory_forgetwhen needed. - Use
memory_transcript_searchif you need evidence from past sessions before editing. - Report what changed and why.
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 First seen · 34 lines · 20 tokens per session scan A c0b6f9e758bb
memory-maintenance is a skill published in the GitHub repository Day1Labs/OpenAva (10 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 259 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
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
project-context
Use PowerContext project memory and handoff tools through MCP when continuing prior work, recalling decisions, maintaining durable memory, or transferring work across tasks, sessions, or agents.
powercontext
Use PowerContext for durable memory, cross-session continuity, and reviewed Experience or Skill artifacts.
fabric-rlm
Recursively decomposes oversized tasks into bounded child Pi agents with fresh context windows. Use for whole-repo audits, massive-context analysis, and multi-file refactors that do not fit one context.