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 xChuCx/agent-memory --skill claudegit clone --depth 1 https://github.com/xChuCx/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/xchucx/agent-memory/claude)<a href="https://agentmods.dev/skills/xchucx/agent-memory/claude"><img src="https://agentmods.dev/badge/skills/xchucx/agent-memory/claude/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/xchucx/agent-memory/claude"><img src="https://agentmods.dev/badge/skills/xchucx/agent-memory/claude.svg" alt="Reviewed on agentmods" width="80" 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.00085 | $0.02387 |
| Opus 5.5 | $0.00034 | $0.00955 |
| Sonnet 5.5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00239 |
Grade A, and why
agent-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 1mo 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.
This is a copy
100% identical to agent-memory — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-memory
agent-memory is a local context middleware that maintains a structured,
byte-preserving Markdown memory layer for this repository. Your runtime
exposes three MCP tools backed by it:
memory.fetch_context— read; returns a budgeted Markdown pack drawn from current task state, conventions, decisions, modules, and (on query) the most relevant indexed sections.memory.propose_update— write; submits structured operations that the server validates, secret-scans, and either applies immediately or stages for human review.memory.status— health; reports file counts, pending staged proposals (with drift status), and security/git/lock posture. Call it when you want to know whether memory needs maintenance before proposing more updates.
At session start: always fetch_context with empty query
{ "name": "memory.fetch_context", "arguments": {} }
The empty-query (“bootstrap”) pack contains:
local/current.<branch>.md— your last working notes on this branch.local/current.shared.md— cross-branch shared state.conventions.md— project conventions.index.md— summary of the memory layout.
Read it carefully before reading source files. It tells you what the team already decided, what footguns are documented, and where you left off.
When else to fetch_context
| Trigger | Call |
|---|---|
| Topic shift mid-task (auth → billing) | fetch_context with a query naming the new topic |
| About to make an architectural decision | fetch_context with a query naming the area |
| Refactoring an unfamiliar module | fetch_context with scope: ["<module-path>"] |
Do not call fetch_context on every tool call. Once at session start
plus query-driven refreshes is the right cadence.
When to propose_update
Pick the intent that matches the situation. Each intent maps to a specific category of memory file and an approval policy.
| Situation | intent |
Routes to |
|---|---|---|
| Working notes on this task, branch-scoped | update_current |
apply |
| Working notes that follow you across branches | update_shared |
apply |
| End-of-task log of what you did | session_log |
apply (path auto-rewritten to sessions/<UTC today>.md) |
| Hit a footgun future-you should avoid | add_pitfall |
apply (when append_to_section) / stage (when rewriting) |
| Made a durable architectural decision | record_decision |
stage |
| Updated facts about a module | refresh_module |
stage |
| Discovered a team convention | update_conventions |
stage |
| An older entry is no longer accurate | archive_stale |
stage |
What ships with it
2 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.
- 1mo ago First seen · 226 lines · 85 tokens per session scan A 72356cb4fb98
agent-memory is a skill published in the GitHub repository xChuCx/agent-memory (15 stars, last pushed 26d ago), licensed Apache-2.0. It adds 85 tokens to every session and 2,387 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-memory, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
stella
Self-knowledge for stella, the self-hosted AI assistant. Use when users ask about configuration, setup, onboarding, providers, models, agents, channels, webhooks, memory, schedules, workflows, goals, workers, skills, plugins, session compaction, notifications, self-update, multi-user behavior, or how stella works.…
recover-context
Extract full context of the last task from the most recent parent session shown in the session lineage. Strategically uses sub-agents to avoid bloating your own context.
octo-summary
Read, create, find, and cite Octo summaries through octo-cli. Use when an agent needs to create an owner-only summary from explicit channels, discover summaries visible to its bot owner, inspect one summary, retrieve its current body, or ground an answer in returned citation metadata. Load after octo-shared.
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
weknora-rag-search
Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.
memory-index
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for…