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 pincerhq/pincer --skill memory-recallgit clone --depth 1 https://github.com/pincerhq/pincerWrote 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/pincerhq/pincer/memory-recall)<a href="https://agentmods.dev/skills/pincerhq/pincer/memory-recall"><img src="https://agentmods.dev/badge/skills/pincerhq/pincer/memory-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/pincerhq/pincer/memory-recall"><img src="https://agentmods.dev/badge/skills/pincerhq/pincer/memory-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.00054 | $0.00411 |
| Opus 5 | $0.00027 | $0.00205 |
| Sonnet 5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
Memory 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 10d 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
Memory recall
Pincer stores per-user memories (facts, preferences, past conversation context) in a persistent backend, separate from the current chat session. Relevant memories are already retrieved automatically and injected into your system prompt as a "Relevant memories about this user" block on every turn — you usually don't need to do anything extra to use them.
When to explicitly search memory
Reach for an explicit memory search tool (if one is registered — look for
memory_search or an MCP-exposed pincer_memory_search tool) when:
- The user references something specific from the past ("what did I tell you about my allergy last month?") that may not have matched the automatic top-3 relevance injection.
- You need more than the ~3 memories already injected into context.
- The user asks a direct "what do you remember about me" question — search broadly rather than relying only on what's already in context.
What gets remembered
Memories are tied to a pincer_user_id (the canonical cross-channel
identity) and are searched by text relevance against the current message.
Each memory is a short fact or note, not a full transcript — don't expect
verbatim conversation recall, expect distilled facts ("prefers metric
units", "allergic to shellfish", "working on a Rust project called Foo").
If the user asks you to forget something
There is no automatic redaction — if a memory-delete capability exists in your current tool set, use it explicitly and confirm back to the user what was removed. If no such tool is available, tell the user honestly that you can't delete stored memories from this session rather than pretending to.
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.
- 10d ago First seen · 40 lines · 54 tokens per session scan A a90c4f5f7024
Memory recall is a skill published in the GitHub repository pincerhq/pincer (50 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 411 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
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…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.