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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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.
[](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/memory)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/memory"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.
<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/memory"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00016 | $0.01229 |
| Opus 5 | $0.00008 | $0.00615 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory — Persistent Memory Management
Manage the project's persistent memory system. This command handles reading, writing, and maintaining the .planning/ memory directory.
Usage
/memory init— Initialize memory for a new project/memory read— Read current memory and display context/memory write— Write session learnings to memory/memory compress— Compress memory when it grows too large/memory status— Show memory system status
Protocol
Initialization (init)
-
Create
.planning/directory structure:MEMORY.md— project brainsessions/— session logssessions/_archive/— archived sessionsdecisions/DECISIONS.md— decision logcontext/architecture.md— architecture notescontext/patterns.md— code patternscontext/gotchas.md— known issuescontext/tech-debt.md— technical debthandoffs/LATEST.md— last session handoffhandoffs/_history/— archived handoffs
-
Codebase Scan Algorithm:
a. DETECT PROJECT TYPE: - package.json → Node.js/JavaScript/TypeScript - requirements.txt/pyproject.toml → Python - go.mod → Go - Cargo.toml → Rust - pom.xml/build.gradle → Java - *.sln/*.csproj → .NET b. EXTRACT TECH STACK: - Parse dependency files for frameworks - Identify major libraries - Note database connections (if visible) c. ANALYZE STRUCTURE: - Count files by extension - Identify source and test directories - Note documentation presence d. GENERATE MEMORY: - Write project overview - Document detected architecture - List identified patterns -
Write initial content to all context files
Read (read)
- Read
.planning/MEMORY.md - Read
.planning/handoffs/LATEST.md(if exists — skip if missing) - Display a summary of project context
- Note any open items or blockers from last session
Write (write)
- Archive previous handoff:
- If
handoffs/LATEST.mdexists, move tohandoffs/_history/YYYY-MM-DD-HHMMSS.md
- If
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.
- 9d ago First seen · 164 lines · 16 tokens per session scan A 343d3ebebbcf
memory is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,229 once invoked, about $0.0001 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.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.