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.
npx agentmods add skills/legacybridge-tech/claude-plugins/memory-statusnpx skills add legacybridge-tech/claude-plugins --skill memory-statusgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWhat 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 | $0.00039 | $0.00682 |
| Opus 5 | $0.00019 | $0.00341 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
memory-status 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Status
Display the current state of the Engram memory system.
When to Use
Use when:
- The user asks about the memory system status
- The user wants to know what's been remembered
- Diagnostics are needed (missing files, empty preferences, etc.)
- The user asks "what do you know about me?"
Workflow
1. Read Configuration
Read .claude/memory-settings.json for:
- Preset type
- File names
- Language
- Search mode
If the file is missing, tell the user to run memory-init first.
2. Inspect Memory Files
For each of the three memory files, gather:
- File exists? (yes/no)
- File size (approximate line count)
- Last modified date (via
statorls -l) - Number of entries:
- Preferences: count of filled (non-empty) fields
- Conversations: count of
### YYYY-MM-DDentries - Long-term: count of
- YYYY-MM-DD:entries
3. Check CLAUDE.md Integration
Verify that CLAUDE.md contains <!-- ENGRAM:START --> / <!-- ENGRAM:END --> markers and an @{PREFS_FILE} reference. This is what auto-loads preferences each session.
4. Display Status Report
Format:
Engram Memory System Status
═══════════════════════════
Configuration:
Preset: <preset>
Language: <language>
Search mode: <strong|weak>
Memory Files:
<preferences-file>
Status: <exists/missing>
Size: <lines> lines
Modified: <date>
Fields: <filled>/<total> filled
<conversations-file>
Status: <exists/missing>
Size: <lines> lines
Modified: <date>
Entries: <count> conversations
<longterm-file>
Status: <exists/missing>
Size: <lines> lines
Modified: <date>
Entries: <count> memories
CLAUDE.md Integration:
ENGRAM section: <present/missing>
@-reference: <present/missing>
Recent Conversations (last 3):
- YYYY-MM-DD HH:MM - Topic
- YYYY-MM-DD HH:MM - Topic
- YYYY-MM-DD HH:MM - Topic
Health Check:
✓ All files present
✓ Preferences populated
✓ CLAUDE.md integration active
✗ No conversation summaries yet
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.
- 3d ago First seen · 101 lines · 39 tokens per session scan A 3a402a11c5af
memory-status is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 682 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…