memory-help

A help guide for a persistent, file-based memory system that stores knowledge globally or per project. It explains the available commands, storage modes, and optional QMD retrieval, a tool for finding related memories.

In plain words
What is it for?
Use it to learn memory commands, understand global versus project notes, check available features, or troubleshoot memory-related questions.
Why use it?
It gives the agent a reference when it is unsure how memory is organised or which command to use.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/pyros-projects/limitless/memory-help
Any agent
npx skills add pyros-projects/limitless --skill memory-help
Clone the repo
git clone --depth 1 https://github.com/pyros-projects/limitless

Made for: Claude Code, Codex.

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00086 $0.02864
Opus 5 $0.00043 $0.01432
Sonnet 5 $0.00017 $0.00573
Haiku 4.5 $0.00009 $0.00286

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

Security

Grade A, and why

memory-help 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/codies-memory/skills/memory-help/SKILL.md · 321 lines

How it starts

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

Memory Help

BETA — This memory system is in active testing. If you encounter bugs, confusing behavior, or have suggestions, run: codies-memory feedback "describe what happened" — your feedback is saved and reviewed.

What This System Is

You have a persistent file-based memory system. It stores what you learn, observe, and decide across sessions. Your vault lives at ~/.memory/<your-agent-name>/. Every command requires --agent <your-agent-name>.

There are two scopes:

  • Global — knowledge that applies across all projects (your identity, cross-project lessons, reflections)
  • Project — knowledge specific to one project (observations, decisions, session summaries)

There are also two practical operating modes:

  • Standalone mode — works with the canonical vault only
  • Full mode — recommended: canonical vault plus QMD retrieval

QMD is recommended when available because recall becomes faster, more token-efficient, and semantic across multiple memory stores. If the user wants that full mode and does not have QMD yet, offer to help install it.


Concepts

Read this section carefully. These terms have specific meanings in this system.

Record Types

Type What it is Scope When to create
inbox A raw observation or note. Unprocessed. project When you notice something worth remembering but haven't decided what it means yet. Use capture.
thread An ongoing investigation or topic you're tracking across sessions. project or global When an inbox item keeps coming up, or you're tracking something over time. Promote from inbox.
lesson A reusable pattern or rule you've learned. "When X, do Y." project or global When you've learned something actionable that applies beyond the current moment. Promote from inbox or thread.
decision A choice that was made with rationale. project or global When a significant decision happens and you want to remember why.
session A summary of one work session. project or _general At the end of every session. If no project vault resolves, it lands in _general.
daily-log Auto-generated append-only cross-project activity index. global only Do not create or edit manually. create and capture append entries automatically.
reflection Philosophical or meta-level thinking. global only When you want to process what something meant, not just what happened.
dream Emotional/subconscious processing. global only Optional. For agents that use creative processing.

Read the full file on GitHub · 321 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. 2d ago First seen · 321 lines · 86 tokens per session scan A c7bfc947e704

Subscribe to this mod's changes

memory-help is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 19d ago), licensed MIT. It adds 86 tokens to every session and 2,864 once invoked, about $0.0004 per session on Opus 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-31.