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/rocketmandrey/claude-recall/skillnpx skills add rocketmandrey/claude-recall --skill skillgit clone --depth 1 https://github.com/rocketmandrey/claude-recallWrote 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/rocketmandrey/claude-recall/skill)<a href="https://agentmods.dev/skills/rocketmandrey/claude-recall/skill"><img src="https://agentmods.dev/badge/skills/rocketmandrey/claude-recall/skill.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.00196 | $0.03960 |
| Opus 5 | $0.00098 | $0.01980 |
| Sonnet 5 | $0.00039 | $0.00792 |
| Haiku 4.5 | $0.00020 | $0.00396 |
Grade B, and why
session-orchestrator scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`cat ~/.claude/session-recaps/handoffs/<полный-id>.md`. How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
session-orchestrator — найти сессию, погрузиться, продолжить
CLI: recall (см. recall help). Данные: ~/.claude/session-recaps/ —
карточка на сессию + единый INDEX.md (строка на сессию). Это первичная точка
касания; запасной полнотекст — recall grep.
Шаг 1 — Поиск по индексу (ВСЕГДА сначала здесь)
recall find <основа1> <основа2> ...
- Ищи по ОСНОВЕ слова, не по словоформе: «Ивановой» →
иванов, «выгрузку» →выгрузк. - Несколько вариантов сразу:
recall find иванов выгрузк постоянн. Выдача уже отранжирована: совпадение в задаче > в #тегах/{сущностях} > в проекте, свежее выше. - Строка индекса:
<id8> <дата>T<чч:мм> <проект> [status] <задача> #теги {сущности}. [new]= сессия ещё без LLM-рекапа (свежая или умершая грязно; строка = её первый запрос). Это НОРМАЛЬНЫЙ кандидат — часто именно та самая последняя сессия.⚡LIVEв конце строки = сессия ОТКРЫТА ПРЯМО СЕЙЧАС. НЕ resume и НЕrecall open(раздвоит контекст) — работай адресно:recall ps→recall peek/send <tty>.(meta)/#meta= сессия-искатель (сама искала другие сессии) — почти никогда не то, что нужно; ранжируется вниз автоматически.- Можно искать прямо по тегу:
recall find #rosperevozki(словарь:recall tags). - Текущую сессию игнорируй. Если индекс молчит — fallback:
recall grep <основы...>(полнотекст по сырым транскриптам; строка:<id8> <дата> <проект> … сниппет …), затем шаг 2 по найденному id. - При «подними последнюю/вчерашнюю сессию» сверяй ВРЕМЯ в строке: одинаковых сессий
одного проекта много, нужна самая свежая по
<дата>T<чч:мм>, не первая попавшаяся.
Несколько кандидатов → селектор
Если уверенного победителя нет (2+ правдоподобных строки) — НЕ выбирай сам. Построй селектор через AskUserQuestion: один вопрос «Какая сессия?», вариант на кандидата (максимум 4 самых свежих/релевантных):
- label — папка проекта + дата (
my-crm · 11.06); - description — контекст из строки индекса: задача, статус, ключевые сущности;
- последним вариантом всегда — «Копнуть глубже»: по выбору открой карточки
(
recall show) всех кандидатов, при нуждеrecall grepили сырые transcripts (~/.claude/projects/), и покажи расширенное сравнение.
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.
- 5d ago First seen · 220 lines · 196 tokens per session scan B 8d8feefa3459
session-orchestrator is a skill published in the GitHub repository rocketmandrey/claude-recall (5 stars, last pushed 2mo ago), licensed MIT. It adds 196 tokens to every session and 3,960 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status, wiki sync, and context recovery. Use for /project-butler, setup/初始化, foundation setup, profile setup, end session/收工…
sync
Fast save-point: sync all session-context files and MEMORY.md with current progress. Zero questions, zero delay. Use when user says /sync, save progress, save state, sync context, or /sync --full for capability inventory.
memory-quality
Audits and cleans up Claude Code auto-saved memory files. Scores on 4 dimensions, detects conflicts, opens a visual dashboard. Trigger on: memories, memory quality, memory cleanup, memory health, memory dashboard, 检查记忆, 清理记忆, 记忆质量, 记忆看板.
dataecho-memory
Persistent memory for agents — durable across sessions, machines, sandboxes, and agent platforms, stored in a private DataEcho cloud drive. Use at the start of a session to recall who the user is and what you were working on; whenever the user says "remember this", "don't forget", "like last time", or references past…
archive
Persistent knowledge wiki and memory system that compounds across conversations using an Obsidian-compatible vault. Consult at the START of any non-trivial task to recall project context, preferences, and past discoveries. Ingest sources and build wiki pages when accumulating knowledge on a topic. Save at the END when…
ccthread
Read, search, and summarize Claude Code conversation history. Use when the user asks to find things discussed in past sessions, review old threads, summarize recent work for teammates, extract learnings into a skill or CLAUDE.md, or answer "what was that value/port/command we used?" — ccthread reads /.claude/projects/…