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 cosmicstack-labs/mercury-agent-skills --skill memory-managementgit clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skillsWrote 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/cosmicstack-labs/mercury-agent-skills/memory-management)<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/memory-management"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/memory-management/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/cosmicstack-labs/mercury-agent-skills/memory-management"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/memory-management.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.00042 | $0.03528 |
| Opus 5 | $0.00021 | $0.01764 |
| Sonnet 5 | $0.00008 | $0.00706 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
memory-management 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 9d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management for Long-Running Agents
Overview
Long-running agents face a fundamental problem: they can't remember everything, but forgetting the wrong thing breaks their usefulness. This skill covers memory architectures that balance context retention, token budget, and retrieval accuracy for agents that run for hours, days, or continuously.
Core Concepts
The Memory Problem
| Issue | Symptom | Cost |
|---|---|---|
| Context Overflow | Agent forgets early instructions | Task failure, incoherent responses |
| Token Bloat | Every message keeps growing | 10x+ cost increase per task |
| Memory Pollution | Irrelevant memories distract agent | Hallucination, off-target responses |
| Stale Memories | Outdated information used as fact | Incorrect decisions |
| Memory Leaks | Unused data accumulates unbounded | Crash from OOM, endless context |
Memory Tiers
| Tier | Storage | Capacity | Access Speed | Cost | Best For |
|---|---|---|---|---|---|
| L1 — Working | In-context (LLM window) | 8K-200K tokens | Instant | $$$ | Current task, immediate context |
| L2 — Recent | Sliding window buffer | ~2K turns | < 10ms | $$ | Recent conversation history |
| L3 — Episodic | Event log / timeseries | Millions of events | < 50ms | $ | Past actions, outcomes, decisions |
| L4 — Semantic | Vector database | Unlimited | < 100ms | $ | Knowledge, facts, relationships |
| L5 — Archival | Object storage | Unlimited | > 1s | $ | Backups, compliance, audit |
Step-by-Step Implementation
Step 1: Build a Tiered Memory System
from dataclasses import dataclass, field
from typing import Optional
import json
import time
@dataclass
class MemoryEntry:
content: str
timestamp: float = None
importance: float = 0.5 # 0.0 (trivial) to 1.0 (critical)
tags: list[str] = field(default_factory=list)
token_count: int = 0
def __post_init__(self):
if self.timestamp is None:
self.timestamp = time.time()
class TieredMemory:
"""Multi-tier memory with automatic promotion and demotion."""
def __init__(self, llm, vector_store, max_context_tokens: int = 8000):
self.llm = llm
self.vector_store = vector_store
self.max_context_tokens = max_context_tokens
# L1: Working context (in-memory)
self.working_memory: list[MemoryEntry] = []
self.current_tokens = 0
# L2: Recent history buffer
self.recent_buffer: list[MemoryEntry] = []
self.buffer_size = 50
# L3: Episodic memory
self.episodes: list[MemoryEntry] = []
# L4: Semantic memory (vector DB)
# Initialized externally
async def remember(self, content: str, importance: float = 0.5,
tags: list[str] = None):
"""Store a new memory across tiers."""
entry = MemoryEntry(
content=content,
importance=importance,
tags=tags or [],
token_count=self._count_tokens(content)
)
# Always add to working memory
self.working_memory.append(entry)
self.current_tokens += entry.token_count
# If important, store in episodic + semantic
if importance > 0.7:
self.episodes.append(entry)
await self.vector_store.store(entry)
# Trim if needed
await self._trim_working_memory()
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.
- 9d ago First seen · 439 lines · 42 tokens per session scan A 96043d5054a0
memory-management is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (471 stars, last pushed 14d ago), licensed MIT. It adds 42 tokens to every session and 3,528 once invoked, about $0.0002 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
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
comet-memory
A review step for deciding whether information should become durable personal memory. It can keep, update, forget, or skip memory candidates based on bounded evidence.
recall-memory
Recall relevant long-term memories on demand. Given a topic or question, judges relevance from pre-loaded metadata, loads only relevant files, and returns a concise summary to the main agent.
agent-expert-creation
Create specialized agent experts with pre-loaded domain knowledge using the Act-Learn-Reuse pattern. Use when building domain-specific agents that maintain mental models via expertise files and self-improve prompts.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…