Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/commands/core/memory.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/memory)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/memory"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/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/luanmorenommaciel/agentspec/memory"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/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.00011 | $0.00685 |
| Opus 5.5 | $0.00004 | $0.00274 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Command
Save session insights to .claude/storage/ for future reference (directory is auto-created on first use).
Usage
/memory # Save current session insights
/memory "specific note to save" # Save with specific context
What It Does
- Analyzes current conversation for valuable insights
- Compresses to high-signal format (decisions, patterns, gotchas)
- Saves to
.claude/storage/memory-{YYYY-MM-DD}.md
When to Use
Use /memory when you've discovered something worth remembering:
- ✅ Non-obvious decisions with rationale
- ✅ Patterns that worked well
- ✅ Gotchas discovered
- ✅ Architecture decisions
- ✅ Terminology clarifications
Don't save:
- ❌ Step-by-step implementation details (obvious from code)
- ❌ Temporary debugging info
- ❌ Every session (only valuable ones)
Output Format
Creates: .claude/storage/memory-{YYYY-MM-DD}.md
# Memory: {date}
> {One-line summary of session}
## Decisions Made
| Decision | Rationale | Impact |
| -------- | --------- | ------ |
| {what} | {why} | {files affected} |
## Patterns Discovered
- {pattern}: {where applied}
## Gotchas
- {gotcha}: {how to avoid}
## Open Items
- [ ] {item for next session}
---
*Saved: {timestamp}*
Process
When invoked:
1. Scan conversation for:
- Decisions (look for "decided", "chose", "will use")
- Patterns (look for reusable solutions)
- Gotchas (look for "gotcha", "watch out", "careful")
- Open items (look for "TODO", "later", "next time")
2. Compress ruthlessly:
- Max 5 decisions
- Max 3 patterns
- Max 3 gotchas
- Max 3 open items
3. Write to storage:
- Create .claude/storage/ if not exists
- Append to existing file if same date
- Use consistent format
Example
User: /memory "Completed authentication refactoring"
→ Scanning conversation...
→ Found: 2 decisions, 1 pattern, 1 gotcha
Saved to: .claude/storage/memory-2026-01-23.md
## Preview:
> Completed authentication refactoring with JWT + refresh tokens
| Decision | Rationale |
| -------- | --------- |
| Use JWT + refresh | Stateless, scales better |
| 15min access token | Balance security/UX |
Pattern: Token rotation on refresh
Gotcha: Must invalidate refresh tokens on password change
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.
- 1mo ago First seen · 136 lines · 11 tokens per session scan A 6e892f139581
memory is a command published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 685 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
discover-genius
Excavate genius from a person's scattered corpus. Produces Genius Profile (what only they uniquely see) + Freedom Path (four-bucket sort of every activity). Gateway to all downstream intelligence systems. For humans, not agents.
orchestrate-brain
Weekly 30-minute second-brain review ritual. Orchestrates inbox clear, lightweight distillation, vault maintenance, cross-reference pass, and next-week capture focus. The compounding rhythm that keeps the system alive.