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-memory-searchnpx skills add apappascs/claude-code-sessions --skill session-memory-searchgit clone --depth 1 https://github.com/apappascs/claude-code-sessionsWrote 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/skills/apappascs/claude-code-sessions/session-memory-search)<a href="https://agentmods.dev/skills/apappascs/claude-code-sessions/session-memory-search"><img src="https://agentmods.dev/badge/skills/apappascs/claude-code-sessions/session-memory-search.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00364 |
| Opus 5 | $0.00031 | $0.00182 |
| Sonnet 5 | $0.00012 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
session-memory-search 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.
What it actually says
Step 1: Run the search
bun run ${CLAUDE_PLUGIN_ROOT}/lib/memory-scanner.ts search "<query>" --limit 20 --context 1
Replace <query> with the user's search term. Add filters based on request:
--type user|feedback|project|reference— filter by memory type--project FILTER— filter by project name--context N— lines of context around each match (default 1)--limit N— max results (default 20)
Step 2: Present the results
Output is NDJSON (one JSON object per line). Parse each line and group results by project.
For each project with matches:
Project: project-name
| File | Type | Line | Match |
|---|---|---|---|
| filename.md | type | N | matched text (trimmed) |
Show context lines (if available) indented below each match.
If no results: Suggest broadening the search or trying alternative keywords.
Step 3: Offer actions
For each matched memory file, the user might want to:
- Read the full file — use the Read tool on the
pathfield - Edit the memory — use the Edit tool on the
pathfield - Check health — suggest
/session-memory-audit
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 · 44 lines · 62 tokens per session scan A 3ead6f44d584
session-memory-search is a skill published in the GitHub repository apappascs/claude-code-sessions (4 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 364 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…