setup

setup is a skill for Claude Code from scitrera/memorylayer. It costs 0 tokens per session (943 once invoked), scanned A, original, Apache-2.0.

An automated setup and checking procedure for MemoryLayer, a service that stores and provides application memory. It checks whether the service is running and configures the permissions needed to use it.

In plain words
What is it for?
Use it to set up MemoryLayer, check its server connection, start it when unavailable, and update local tool permissions without removing existing ones.
Why use it?
It removes manual setup checks and can identify a missing service or permission before memory features are used.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the memorylayer plugin — 1 skill, 4 commands, 6 hooks, 1 MCP server shipped together

Good fit Use it to set up MemoryLayer, check its server connection, start it when unavailable, and update local tool permissions without removing existing ones.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/scitrera/memorylayer/setup
Install

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.

Any agent
npx skills add scitrera/memorylayer --skill setup
Clone the repo
git clone --depth 1 https://github.com/scitrera/memorylayer

Made for: Claude Code.

Or install memorylayer, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 6 hooks, 1 MCP server.

Wrote 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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/scitrera/memorylayer/setup/github.svg)](https://agentmods.dev/skills/scitrera/memorylayer/setup)
Your own site
<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.

agentmods 80×15 button for setup

Your own site · 80×15
<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>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 943 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash d8bd44afc05b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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
memorylayer-cc-plugin/skills/setup/SKILL.md · 127 lines

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:

  1. Store: memory_remember with content "MemoryLayer setup verification test" and tags ["setup-test"]
  2. Recall: memory_recall with query "setup verification test" — verify the test memory is returned
  3. Forget: memory_forget with the memory ID from step 1 — clean up the test memory

If any step fails, report the error and suggest checking server logs.

Read the full file on GitHub · 127 lines

Changes

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.

  1. 1mo ago First seen · 127 lines · 0 tokens per session scan A d8bd44afc05b

Subscribe to this mod's changes

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.

Related

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…

mem0ai/mem0 · 217 tokens

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…

asgeirtj/system_prompts_leaks · 74 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens

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.

GanyuanRan/Aegis · 45 tokens