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 skills add matteotitta/genesys-skills --skill recallgit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/recall)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/recall"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/recall/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/skills/matteotitta/genesys-skills/recall"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.01866 |
| Opus 5 | $0.00062 | $0.00933 |
| Sonnet 5 | $0.00025 | $0.00373 |
| Haiku 4.5 | $0.00012 | $0.00187 |
Grade A, and why
recall 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 11d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recall — Search past sessions and surface decisions
Search your Claude Code session history instantly. Instead of starting from zero each conversation, recall what was discussed, decided, and built in past sessions.
For full mode workflows (topic / temporal / client / decisions / stats), output formats, and indexer maintenance → the premium reference.
Claude Code Triggers
Invoke this skill when user says:
- "/recall [topic]"
- "/recall yesterday" or "/recall last week"
- "/recall --client [name]"
- "/recall --decisions"
- "What did we decide about...?"
- "Pick up where I left off on..."
- "Find the session where we..."
- "What was I working on yesterday?"
Do NOT invoke when:
- User wants to search files in current codebase (use Grep/Glob)
- User wants to search Slack, email, or Linear (use
/todayor direct MCP) - User is asking about something in the current conversation (just answer)
Modes (quick reference)
| Mode | Purpose | Required arg |
|---|---|---|
/recall [topic] |
BM25-ranked search across all sessions | topic |
/recall yesterday / last week / [date] |
Temporal browse | time range |
/recall --client [name] |
Filter by client | client name |
/recall --decisions |
Surface extracted decisions | optional client/days filter |
/recall --memory [topic] |
Tier-boosted search across durable memory pages (G13) | topic |
/recall --stats |
Index health stats (now includes memory page count + orphan count) | none |
For full mode workflows + output formats → the premium reference.
--memory mode (G13 — added 2026-05-23)
Searches the memory_pages table (~/.claude/.../memory/*.md) with tier-boosted ranking distinct from session-content search. Use this mode when the question is about durable rules, voice, preferences, or canonical references rather than past session conversation.
Tier boosts (multiplier on BM25 rank):
| Type prefix | Boost | Reasoning |
|---|---|---|
feedback_* |
1.5x | Durable voice/quality rules — highest signal |
reference_* |
1.4x | Canonical references (people, repos, conventions) |
project_* |
1.3x | Active engagement state |
user_* |
1.2x | User preferences |
| unknown | 1.0x | Fallback |
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.
- 11d ago First seen · 183 lines · 124 tokens per session scan A 967ee9c725c6
recall is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 1,866 once invoked, about $0.0006 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-30.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
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.…
add-editor
Wire Deus's memory + evolution layers into an external code editor (Zed and other ACP/MCP clients) so the editor's own agent gains Deus's vault recall and self-improving reflexion loop. Configuration only — no new code. Triggers on "add editor", "use Deus in my editor", "zed integration", "editor integration", "wire…
resume
Load context from permanent memory and recent session logs. Tiered loading — CLAUDE.md full, session logs frontmatter-only by default.