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/acn-ericlaw/agent-memory/archive-factnpx skills add acn-ericlaw/agent-memory --skill archive-factgit clone --depth 1 https://github.com/acn-ericlaw/agent-memoryWrote 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/acn-ericlaw/agent-memory/archive-fact)<a href="https://agentmods.dev/skills/acn-ericlaw/agent-memory/archive-fact"><img src="https://agentmods.dev/badge/skills/acn-ericlaw/agent-memory/archive-fact.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.00081 | $0.01021 |
| Opus 5 | $0.00041 | $0.00511 |
| Sonnet 5 | $0.00016 | $0.00204 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
archive-fact 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ Tool-managed skill provided by agent-memory (
provenance: agent-memory-builtin). Don't edit it in place — fork under a new name, or upstream a fix to the agent-memory project (seeSKILLS.md).
This skill is the safe archive-move. It performs REVIEW.md step 4 — moving a faded/superseded fact's
block out of the live layer — continuity.md, or a thread's own memory/open-threads/thread-<id>.md
file (v4.39.0; the sweep moves the block to the quarter archive and deletes the file) — as a runnable script, so the move can't be
botched. Don't hand-edit continuity.md to do this (the read-modify-write open(f,"w").write(open(f).read()+…)
truncates the file before the read — it has wiped a version.md stamp and then this repo's archive,
50 facts → 6, once each). This script reads the whole file into memory first and writes once, so truncation
is structurally impossible.
What it does NOT do
It does not decide what to archive — that judgment (which facts have faded, contradiction scans,
supersession) stays with the agent and the REVIEW.md ritual (never-pick-a-winner). This is the
mechanical executor only: you name the id(s); it moves them. Same split as memory-lint (the script counts;
the agent judges).
How to run
From the repo root, use whichever runtime the machine has (output is byte-identical):
python3 agent-skills/archive-fact/scripts/archive-fact.py --id <fact-id> [--id <fact-id> …]
# or
node agent-skills/archive-fact/scripts/archive-fact.mjs --id <fact-id> [--id <fact-id> …]
Flags:
--id ID— the fact/thread id to archive (repeatable; the move is all-or-nothing — if any id is missing it refuses and changes nothing).--reason—faded(default) or e.g."superseded by <new-id>".--quarter YYYY-Qn— targetmemory/archive/<quarter>.md(default: derived from today, UTC).--note TEXT— theINDEX.mdone-liner (single--idonly; otherwise derived from the block).--dry-run— print what would move; change nothing. Preview first when unsure.
What ships with it
4 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.
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 Changed · +1 lines e3fc9710aee6
- 5d ago First seen · 62 lines · 81 tokens per session scan A b2925ec8a168
archive-fact is a skill published in the GitHub repository acn-ericlaw/agent-memory (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 1,021 once invoked, about $0.0004 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
Context Doctor
Identify and repair degradation in system prompt, external memory, and skills preventing you from following instructions or remembering information as well as you should.
memanto-companion
Inspect and manage the cross-session engineering memory that Memanto maintains for your Claude Code skills. Use when the user asks what Memanto remembers, wants to see their engineering profile, manually recall context for a skill, or store a decision. The automatic lifecycle hooks handle capture/injection on their…
system-monitor
Monitor system health: CPU, memory, disk, processes, and network. Alert on thresholds via any channel.
ov-experience-memory
Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.