memory

memory is a command for Claude Code, Cursor from yonatangross/orchestkit. It costs 77 tokens per session (1,611 once invoked), scanned A, original, MIT.

A read-only memory command for searching stored knowledge, loading session context, viewing decision history, checking status, and displaying relationships as a graph. A knowledge graph is a map of connected facts or decisions.

In plain words
What is it for?
Use it to search prior decisions, continue earlier work, inspect history, check memory status, or visualize connected project information.
Why use it?
Important project decisions and context can be spread across sessions. This brings relevant past information back when you need it without loading everything at once.

Command for Claude CodeCursor

Written for Claude Code and Cursor: allowed-tools in frontmatter, but also a Cursor plugin manifest. Also seen: model in frontmatter; reads .claude/ paths; names the AskUserQuestion tool.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 skills/memory/scripts/staleness_cron.py docs/reports/ \.

Part of the ork plugin — 111 skills, 38 commands, 36 agents, 32 hooks shipped together

Good fit Use it to search prior decisions, continue earlier work, inspect history, check memory status, or visualize connected project information.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit
agentmods
npx agentmods add commands/yonatangross/orchestkit/memory

Made for: Claude Code, Cursor.

Or install ork, the plugin that ships this one along with the rest of its 111 skills, 38 commands, 36 agents, 32 hooks.

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 memory

README.md
[![agentmods](https://agentmods.dev/badge/commands/yonatangross/orchestkit/memory/github.svg)](https://agentmods.dev/commands/yonatangross/orchestkit/memory)
Your own site
<a href="https://agentmods.dev/commands/yonatangross/orchestkit/memory"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/memory/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 memory

Your own site · 80×15
<a href="https://agentmods.dev/commands/yonatangross/orchestkit/memory"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,611 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.01611
Opus 5.5 $0.00031 $0.00644
Sonnet 5.5 $0.00015 $0.00322
Haiku 4.5 $0.00008 $0.00161

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

Security

Grade A, and why

memory 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 17d 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/ork/.cursor-plugin/commands/memory.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auto-generated from skills/memory/SKILL.md

Source: https://github.com/yonatangross/orchestkit

Memory - Read & Access Operations

Unified read-side memory skill with subcommands for searching, loading, syncing, history, and visualization.

Cross-session read strategy (Opus 5.5 / CC 2.1.111+): Opus 5.5 reads filesystem memory reliably across sessions. When loading context at session start, prefer the layered read order:

  1. ~/.claude/projects/<slug>/memory/MEMORY.md (durable index — load first, always)
  2. .claude/chain/state.json + most recent NN-*.json handoff (session continuation)
  3. MCP mcp__memory__search_nodes for anything the filesystem index doesn't answer (typed graph traversal)

Layer 1 is cheap (small index file), Layer 2 is scoped (session-specific), Layer 3 is selective (only when needed). Avoid dumping the full knowledge graph into context — use the index to narrow the search first.

Argument Resolution

SUBCOMMAND = "$ARGUMENTS[0]"  # First token: search, load, history, viz, status
QUERY = "$ARGUMENTS[1]"       # Second token onward: search query or flags
# $ARGUMENTS is the full string (CC 2.1.59 indexed access)

Usage

memory search <query>  # Search knowledge graph
memory load             # Load context at session start
memory history          # View decision timeline
memory viz              # Visualize knowledge graph
memory status           # Show memory system health

CRITICAL: Use AskUserQuestion When No Subcommand

If invoked without a subcommand, ask the user what they want:

AskUserQuestion(
  questions=[{
    "question": "What memory operation do you need?",
    "header": "Operation",
    "options": [
      {"label": "search", "description": "Search decisions and patterns in knowledge graph"},
      {"label": "load", "description": "Load relevant context for this session"},
      {"label": "history", "description": "Decision timeline + knowledge-graph viz (--mermaid)"},
      {"label": "status", "description": "Check memory system health"}
    ],
    "multiSelect": false
  }]
)

Read the full file on GitHub · 154 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. 17d ago Changed 0c5c749bcb7c
  2. 21d ago Changed · +13 tokens per session ed2c44e89279
  3. 24d ago Changed 17209d86ed89
  4. 1mo ago Changed 1caefcc68145
  5. 1mo ago Changed 4240c90acee8
  6. 1mo ago First seen · 154 lines · 64 tokens per session scan A feec06b069d3

Subscribe to this mod's changes

memory is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,611 once invoked, about $0.0003 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-08-30.