What is memory-lagestand?

A skill for saving selected project status, decisions, completed work, preferences, and lessons in StudioMeyer Memory, a system for storing project context.

Use it to curate project updates, decisions, rules, preferences, lessons, and related entity facts, while reading back what was saved.

It records useful conclusions as separate, durable notes instead of keeping them only in a conversation.

memory-lagestand — Skill for Claude Code by studiomeyer-io

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 studiomeyer-io/studiomeyer-marketplace --skill memory-lagestand

Clone the repo

git clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplace

Made for: Claude Code.

Or install studiomeyer-memory-chat, the plugin that ships this one along with the rest of its 4 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand/github.svg)](https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand)

Your own site

<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-lagestand.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 325 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.00325
Opus 5.5	$0.00013	$0.00130
Sonnet 5.5	$0.00007	$0.00065
Haiku 4.5	$0.00003	$0.00032

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

Security

Grade A, and why

memory-lagestand 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 2d 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.

plugins/studiomeyer-memory-chat/skills/memory-lagestand/SKILL.md · 17 lines

What it actually says

Curate a Memory status

Build a small set of durable entries from the user's stated outcome. Keep rules, completed work, rejected options, preferences, decisions, and lessons distinct. Do not transmit the whole conversation.

Read the relevant previous state with nex_recall, nex_search, or nex_sprint when a correction or conflict may matter.
Phrase each proposed entry as one clear assertion. For a mistake, capture the cause and useful correction. Mark uncertain conclusions as tentative.
When the user asked for suggestions, show the proposed entries and wait for their selection. When exact content was already selected, save it without requesting a second confirmation.
Use nex_decide for a real choice and its reasoning; use nex_learn for a lesson, rule, preference, or workflow. Use nex_entity_observe or nex_entity_relate for a graph fact or link. Update nex_sprint only when the user asked to maintain that working state.
Read back the affected entry when practical and report whether it was added, updated, skipped, or rejected. Use nex_session_end only when the user explicitly ends the session.

Do not silently remove or supersede older entries. Use the server's dedicated update or invalidation tools only after the affected record and requested change are clear.

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.

2d ago First seen · 17 lines · 33 tokens per session scan A b3492a16bfc4

Subscribe to this mod's changes

memory-lagestand is a skill published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 325 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.

Claude Code Memory and context agent-personas ai-memory claude-code-plugin crm geo

memory-protocol

A shared set of rules for using a persistent memory service across coding-agent sessions.

vbcherepanov/total-agent-memory · 120 tokens

memory

Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…

vbcherepanov/total-agent-memory · 65 tokens

engram-digest

Seed or top up this project's Engram graph from the existing codebase — an explicit, user-invoked digestion of the current working tree into typed memory nodes (decisions, principles, cautions, problems, insights, intents). Use when the user says "digest this project", "ingest the codebase into memory", "seed the…

techtheist/engram · 98 tokens

engram

Read and write the project's durable reasoning memory (decisions, principles, cautions, problems, insights) through the Engram MCP tools. Recall relevant memory before non-trivial work; capture only durable, high-value knowledge silently at natural stopping points; keep the graph honest (judge suspects, close answered…

techtheist/engram · 78 tokens

session-recap

Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.

sxhmilyoyo/sundayhao-plugins · 39 tokens

garden-tending

Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…

linxule/memex-plugin · 131 tokens