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/scitrera/memorylayer/setupnpx skills add scitrera/memorylayer --skill setupgit clone --depth 1 https://github.com/scitrera/memorylayerWhat 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.00000 | $0.00943 |
| Opus 5 | $0.00000 | $0.00472 |
| Sonnet 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 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.
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.
- yesterday 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 3mo 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…