Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add strvmarv/total-recall/plugin install total-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/strvmarv/total-recall/commands)<a href="https://agentmods.dev/skills/strvmarv/total-recall/commands"><img src="https://agentmods.dev/badge/skills/strvmarv/total-recall/commands.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.1 | $0.00061 | $0.04379 |
| Opus 5 | $0.00030 | $0.02190 |
| Sonnet 5 | $0.00012 | $0.00876 |
| Haiku 4.5 | $0.00006 | $0.00438 |
Grade B, and why
total-recall:commands 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 6d 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.
Auto-configure Claude Code permissions so total-recall MCP tools are allowed (required for TUI fullscreen / `dontAsk` permission mode). **This subcommand is Claude Code-specific** — it automates `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMMEDIATE ACTION REQUIRED — before responding to the user's first message, call the total-recall session_start MCP tool. This syncs host imports and loads hot tier context. If session_start has already run server-side, the call returns cached results instantly.
If session_start is blocked by permissions (e.g., in TUI fullscreen / dontAsk mode), do NOT just report the error. Instead:
- Tell the user: "total-recall session_start was blocked by permissions. Your host's tool-permission settings need to allow total-recall's MCP tools to function (the exact tool name depends on how your host namespaces MCP tools). You may need to adjust permissions if you want total-recall active this session."
- On Claude Code, suggest running
/total-recall:commands setupto auto-configure permissions; other hosts don't have an automated fix yet — point the user at their host's own MCP tool-permission config. - Proceed without memory features for this session — memory unavailability is degraded mode, not fatal
total-recall
Memory and knowledge base management for total-recall.
Automatic Behavior
These behaviors run automatically throughout the session. Tool calls will be visible to the user.
Session Start
- Call the
session_startMCP tool to sync imports and assemble hot tier context (this may already be cached — call it regardless to receive the context) - Announce startup using the returned data:
- Report tier summary: pinned, hot, warm, cold, KB counts from
tierSummary - Report storage backend from
storage(e.g. "sqlite", "cortex", "postgres"). If it shows a fallback like "sqlite (cortex failed)", flag this prominently. - If
lastSessionAgeis present, mention when the last session was - If
hintsare present, briefly surface the most relevant ones - If
pinned_budget_pressureis present inhints, surface it prominently: pinned entries are eating over half the context budget — suggest unpinning or trimming entries - Keep it to 2-3 lines max. Example:
total-recall loaded — 2 pinned, 3 hot, 12 warm, 5 cold, 2 KB collections. Storage: cortex. Last session: 2 hours ago. Context: TODO list at docs/TODO.md; user prefers bundled PRs for refactors.
- Report tier summary: pinned, hot, warm, cold, KB counts from
- Use
hintsto inform your behavior throughout the session — they represent high-value memories like user corrections, preferences, and frequently accessed project context - Incorporate the full
contextfield to inform your responses
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.
- 6d ago First seen · 332 lines · 61 tokens per session scan B b23c9683628e
total-recall:commands is a skill published in the GitHub repository strvmarv/total-recall (14 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 4,379 once invoked, about $0.0003 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-30.
Other skills, from other repositories
hermes-history-ingest
Ingest Hermes agent history into the Obsidian wiki. Use this skill when the user wants to mine their past Hermes sessions for knowledge, import their /.hermes folder, extract insights from previous Hermes conversations, or says things like "process my Hermes history", "add my Hermes memories to the wiki", "ingest…
wiki-narrate
Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.
session-brain
Build and maintain a topic graph over your agent session history. Reads every Claude session transcript plus the pruned sessions that survive only in history.jsonl, clusters them by topic using local TF-IDF (no API calls, no embeddings), and writes an interactive graph you can open in a browser. Use when the user says…
wiki-context-pack
Produce a token-bounded, citation-ready context slice from an existing Obsidian vault for a downstream agent or task. Use for "/wiki-context-pack", "use my vault as context", "context slice for X", "pack the wiki for my agent", or "bounded context for Y".
context-engineering
项目级上下文工程框架:通过 PROJECT / REQUIREMENTS / ROADMAP / STATE 四层文档 为每个任务建立结构化上下文,控制 token 预算,防止上下文腐烂, 确保跨会话连续性。与 context-lifecycle 的 L0-L3 层互补。.
error-experience-library
错误经验库:自动捕获错误模式、根因和解决方案,支持查询和反馈更新。 当遇到 build error、runtime error 或需要查找历史错误解决方案时使用。.