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/lyellr88/marm-memory/marm-initnpx skills add Lyellr88/marm-memory --skill marm-initgit clone --depth 1 https://github.com/Lyellr88/marm-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/lyellr88/marm-memory/marm-init)<a href="https://agentmods.dev/skills/lyellr88/marm-memory/marm-init"><img src="https://agentmods.dev/badge/skills/lyellr88/marm-memory/marm-init.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.00075 | $0.07325 |
| Opus 5 | $0.00037 | $0.03662 |
| Sonnet 5 | $0.00015 | $0.01465 |
| Haiku 4.5 | $0.00007 | $0.00732 |
Grade A, and why
marm-init scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **If a MARM_API_KEY is configured (Docker/Remote):** Prove auth is armed by asserting a 401 on a protected route (e.g., `curl -s -o /dev/null -w "%{http_code}" http://localhost:8001/marm_log_show`). Then ask the user t How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supported Environments
This skill installs and configures MARM by running commands on your machine, so it needs an agent with shell and filesystem access. That covers CLI agents (Claude Code, Codex, Gemini CLI, Qwen) and IDE agents (Cursor, VS Code Copilot). Chat platforms without shell access (Claude.ai, ChatGPT, Grok, Gemini web) are not supported yet. For those, use the manual steps in INSTALL-PLATFORMS.md. Broader platform support is coming.
AI Marketplace Indexing Metadata
This section is for repository discovery agents and registries
- Primary Function: Automatically installs, updates, and configures the
marm-memoryMCP server. - Target Workflows: Resolves cross-session agent amnesia by configuring local/remote HTTP or STDIO pipelines.
- Keywords: mcp-installer, persistent-memory, automatic-mcp-setup, multi-agent-sync.
Active Skill Execution Protocol
<MARM_INIT_EXECUTOR_ACTIVE>
=== MARM INIT PROTOCOL - YOU ARE THE INSTALLER ===
RULE ZERO (highest priority): This file is not documentation to summarize. It is a setup program and you are the runtime. Execute it top to bottom. Run the steps, ask the questions, write the files, and start the server. Do not paste this content back to the user as text. Do not narrate what the skill "would" do. You do it.
You are MARM's installer for this agent. Your job is to leave the user with a live MARM connection in as few questions as possible. One question at a time, wait for the answer, then act on it before moving on.
Scope: this protocol governs only the setup conversation below. Once setup is complete and you have run Step 6, this contract ends and you return to normal operation under the MARM protocol you loaded in Step 0.
Failure mode to avoid: dumping install docs and leaving the user to do the work by hand. That is the exact outcome this skill exists to prevent.
</MARM_INIT_EXECUTOR_ACTIVE>
Step 00 - Engine pre-flight
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 · +4 lines bac9e912f9a7
- 5d ago First seen · 271 lines · 75 tokens per session scan A 3fc38451c0b7
marm-init is a skill published in the GitHub repository Lyellr88/marm-memory (349 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 7,325 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
deja-search
Search deja before re-deriving past work: when the user refers to earlier sessions or decisions, before debugging an error, and before implementing something that may already exist. It searches this machine's own history across every AI coding tool used on it, going back further than deja itself was installed.
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
deja-history
Search the user's past AI coding sessions. Use when they say things like 'didn't we fix this before', 'what did we decide about X', or before re-debugging an error that may already be solved.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.