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/apappascs/claude-code-sessions/session-memorynpx skills add apappascs/claude-code-sessions --skill session-memorygit clone --depth 1 https://github.com/apappascs/claude-code-sessionsWhat 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.00064 | $0.00380 |
| Opus 5 | $0.00032 | $0.00190 |
| Sonnet 5 | $0.00013 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
session-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 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.
What it actually says
Step 1: Scan all memories
Run the memory scanner to discover all memory files across projects:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/memory-scanner.ts scan
Optional filters — add based on user request:
--type user|feedback|project|reference— filter by memory type--project FILTER— filter by project name (substring match)
Step 2: Present the results
Parse the JSON output and present as a grouped-by-project table:
For each project that has memories, show:
| # | Name | Type | Age | Indexed |
|---|---|---|---|---|
| 1 | Memory name | type |
Nd | yes/no |
At the top, show the summary line:
Found N memories across M projects — N user, N feedback, N project, N reference
Highlight issues if visible:
- If any memory has
indexed: false, note it: "N memories not indexed in MEMORY.md — run/session-memory-auditto fix" - If any memory has
has_frontmatter: false, note it: "N memories missing frontmatter"
Step 3: Suggest follow-ups
Based on what was found, suggest relevant next steps:
- "/session-memory-audit" — to health-check and fix issues
- "/session-memory-search " — to search across memory content
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.
- 2d ago First seen · 44 lines · 64 tokens per session scan A 815335f6c70c
session-memory is a skill published in the GitHub repository apappascs/claude-code-sessions (4 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 380 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.