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/agentculture/learn-cli/recallnpx skills add agentculture/learn-cli --skill recallgit clone --depth 1 https://github.com/agentculture/learn-cliWhat 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.00279 | $0.02365 |
| Opus 5 | $0.00139 | $0.01182 |
| Sonnet 5 | $0.00056 | $0.00473 |
| Haiku 4.5 | $0.00028 | $0.00236 |
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 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.
This is a copy
98% identical to recall — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recall — search the shared eidetic memory
recall drives eidetic recall: given a query, it returns the top-k stored
records ranked by relevance, each with its text, full metadata (provenance),
a numeric score, and a freshness signal. It is the read half of the memory
surface; the write half is the sibling /remember skill.
The point of a shared store is that memory is a team faculty, not a
per-agent silo: a record Claude wrote is recallable by the colleague backend
(and vice versa), because both resolve the same ~/.eidetic/memory path.
How to run
bash .claude/skills/recall/scripts/recall.sh "<query>" [flags...]
The wrapper resolves the CLI portably (installed eidetic on PATH, else
uv run eidetic from the checkout) and forwards every flag verbatim, so it is
exactly eidetic recall …. Run it from anywhere; the store is the same.
Search modes (--mode, default hybrid)
| Mode | What it matches | Needs embed server? |
|---|---|---|
exact |
case-insensitive verbatim substring (--case-sensitive to tighten) |
no — offline-safe |
approximate |
vector cosine / semantic similarity | yes (falls back offline) |
keyword |
BM25 lexical; only records sharing a query term | no — offline-safe |
hybrid |
alpha*approximate + (1-alpha)*keyword (--alpha, default 0.5) |
uses it when up |
hybrid is the default because the two signals cover each other's blind spots:
vector catches paraphrases, keyword catches exact ids/quotes. When the embed
server is unreachable, hybrid collapses to keyword-only (it never fuses
meaningless offline-fallback cosine).
Output fields
Each hit in --json output includes:
| Field | Notes |
|---|---|
id |
stable record identity |
text |
the stored chunk |
type |
record type |
metadata |
full provenance, round-tripped verbatim from ingest |
score |
relevance score from the chosen search mode (freshness-blended) |
signal |
freshness strength in [0, 1]; computed at recall time from age, recall frequency, and staleness |
created |
ISO-8601 ingest date (may be DATE_UNKNOWN for legacy records) |
last_recall |
ISO-8601 timestamp of the most recent recall hit (null if never recalled) |
recall_count |
number of times this record has been recalled (passive reinforcement counter) |
lifecycle |
active, shadowed, or archived |
links |
list of related-memory ids |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 182 lines · 279 tokens per session scan A c2368c7c10f0
recall is a skill published in the GitHub repository agentculture/learn-cli (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 279 tokens to every session and 2,365 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to recall, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…