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 scitrera/memorylayer --skill setupgit clone --depth 1 https://github.com/scitrera/memorylayerWrote 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/scitrera/memorylayer/setup)<a href="https://agentmods.dev/skills/scitrera/memorylayer/setup"><img src="https://agentmods.dev/badge/skills/scitrera/memorylayer/setup/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/scitrera/memorylayer/setup"><img src="https://agentmods.dev/badge/skills/scitrera/memorylayer/setup.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.00000 | $0.00943 |
| Opus 5.5 | $0.00000 | $0.00377 |
| Sonnet 5.5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
setup 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://localhost:61001/health How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MemoryLayer Setup Skill
Automated setup and verification for MemoryLayer.
Activation
This skill activates when users ask about:
- Setting up MemoryLayer
- Configuring memory settings
- Troubleshooting memory issues
Instructions
When this skill is activated, perform the following steps automatically. Do not just describe the steps — execute them.
Step 1: Check Server Connection
Run a health check against the MemoryLayer server:
curl -sf http://localhost:61001/health
If the server is unreachable, offer to install and start it:
pip install memorylayer-server
memorylayer serve &
Wait a few seconds after starting, then re-check health.
Step 2: Auto-Configure Permissions
Check if MemoryLayer tool permissions are already configured. Read .claude/settings.local.json (create the file if it doesn't exist). If the permissions allow list does not include the memorylayer wildcard, add it:
{
"permissions": {
"allow": [
"mcp__plugin_memorylayer_memorylayer__*"
]
}
}
Important: If .claude/settings.local.json already exists, read it first and merge the permission into the existing allow array. Do not overwrite other settings.
Step 3: Verify MCP Tools
Call memory_briefing to confirm the MCP tools are connected and working. This simultaneously:
- Verifies the MCP server is running
- Verifies the SDK can communicate with the MemoryLayer server
- Returns workspace stats
If this fails, check that the plugin is installed (/plugin list) and that the server is running (Step 1).
Step 4: Run Smoke Test
Perform a store-recall-forget cycle to verify end-to-end functionality:
- Store:
memory_rememberwith content "MemoryLayer setup verification test" and tags ["setup-test"] - Recall:
memory_recallwith query "setup verification test" — verify the test memory is returned - Forget:
memory_forgetwith the memory ID from step 1 — clean up the test memory
If any step fails, report the error and suggest checking server logs.
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 · 127 lines · 0 tokens per session scan A d8bd44afc05b
setup is a skill published in the GitHub repository scitrera/memorylayer (2 stars, last pushed 24d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 943 tokens. 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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.