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/richfrem/agent-plugins-skills/memory-managementnpx skills add richfrem/agent-plugins-skills --skill memory-managementgit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/memory-management)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/memory-management"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/memory-management.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.00027 | $0.00487 |
| Opus 5 | $0.00014 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 yesterday.
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 Management (3-Layer Filesystem Engine)
Zero-dependency memory system providing high-speed cognitive continuity across agent sessions without external vector databases or daemon processes.
The 3 Filesystem Layers
-
Layer 1: Runtime Context (Lean Procedural Core)
- Lean
SKILL.mdfiles (target <= 100 lines). - Loaded strictly on-demand.
- Inference Restriction: Historical raw execution traces and multi-page wiki dossiers are barred during active task execution to eliminate context window bloat.
- Lean
-
Layer 2: Compounding Wiki Layer (Permanent Knowledge)
- Permanent Markdown documents stored in
wiki/and pluginreferences/. - Contains: domain playbooks, known edge cases, negative constraints,
map-debt.md, andevolution-log.md. - Knowledge Status Taxonomy: Entries are tagged with explicit confidence (
OBSERVED,HYPOTHESIS,CONFIRMED,REJECTED,OPEN). - Confidence Decay: Knowledge not re-verified within 30 days decays from
CONFIRMEDtoOBSERVED. - Asymmetric Persistence Rule: When an evolution attempt fails, code mutations are rolled back, but wiki insights, edge-case discoveries, and failure logs are NEVER rolled back.
- Permanent Markdown documents stored in
-
Layer 3: Safe Audit Layer (Append-Only Manifests)
- Stored in
.agent/learning/traces/cycle_manifests.jsonl. - Tracked audit log capturing event sequences, hashes, exit codes, and affected paths (zero raw terminal text or credentials).
- Audited exclusively via
verify_evolution_receipt.py.
- Stored in
Standardized Retrieval Protocol
All memory lookups use native filesystem tools:
- Targeted Exact Match:
rg "<symbol-or-pattern>" <dir>orgrep_search. - Playbook Inspection: Direct file read of
references/<topic>-playbook.mdorwiki/<topic>.md. - Map Debt Audit: Scan
references/map-debt.mdfor existing open friction items before starting tasks.
What ships with it
14 files 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.
- acceptance-criteria.md 1.2 KB
- assets/resources/memory_architecture.mmd 51 B
- assets/resources/memory_lookup_flow.mmd 50 B
- assets/resources/memory_session_lifecycle.mmd 56 B
- evals/evals.json 1.2 KB
- evals/results.tsv 301 B
- fallback-tree.md 1.3 KB
- references/acceptance-criteria.md 42 B
- references/cheapest_models.json 40 B
- references/cheapest_models.md 38 B
- references/diagrams/architecture/memory_architecture.mmd 71 B
- references/diagrams/architecture/memory_lookup_flow.mmd 70 B
- references/diagrams/architecture/memory_session_lifecycle.mmd 76 B
- references/fallback-tree.md 36 B
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.
- yesterday First seen · 37 lines · 27 tokens per session scan A a77455119870
memory-management is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 487 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-09-03.
Other skills, from other repositories
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
todos
Handle the agent personal todos.md file.