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 strvmarv/total-recall --skill using-total-recallgit clone --depth 1 https://github.com/strvmarv/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/using-total-recall)<a href="https://agentmods.dev/skills/strvmarv/total-recall/using-total-recall"><img src="https://agentmods.dev/badge/skills/strvmarv/total-recall/using-total-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/strvmarv/total-recall/using-total-recall"><img src="https://agentmods.dev/badge/skills/strvmarv/total-recall/using-total-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 108 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00030 | $0.02115 |
| Opus 5.5 | $0.00012 | $0.00846 |
| Sonnet 5.5 | $0.00006 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
using-total-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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using total-recall
This skill ensures the total-recall memory system is active for this session.
Immediate Action
- Call the total-recall
session_startMCP tool now (if it already ran server-side, it returns cached results instantly) - If
session_startis blocked by permissions (e.g., in TUI fullscreen /dontAskmode):- 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 for future sessions; 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 — this is degraded mode, not fatal
- 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 - If
backgroundTasks.reindexshowsstate: "running", tell the user a one-time embedding re-index is in progress (done/total): local semantic retrieval is degraded until it completes. It runs in the background and the server is fully usable meanwhile — re-check via thestatustool or the nextsession_start. (This is normal after an embedding-model change or upgrade; it is not an error.) - If
backgroundTasks.setupis present (event: "provisioned"), briefly note that first-run setup finished (the memory engine was downloaded) — a one-time message - Keep it to 2-3 lines max
- Report tier summary: pinned, hot, warm, cold, KB counts from
- Use
hintsto inform your behavior throughout the session - Incorporate the returned context to inform your responses
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.
- 1mo ago First seen · 129 lines · 30 tokens per session scan A a4421a830f57
using-total-recall is a skill published in the GitHub repository strvmarv/total-recall (15 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 2,115 once invoked, about $0.0001 per session on Opus 5.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
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
hermes-history-ingest
Ingest Hermes agent history into Obsidian as distilled knowledge. Use for importing or mining /.hermes sessions, memories, or logs; use wiki-agent for targeted topic-only cross-agent recall.
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 or refresh a browser-viewable topic graph over Claude session history using local clustering. Use for mapping or clustering sessions, recent or stale topic analysis, or rebuilding/showing the session graph. Unlike wiki-history-ingest, it indexes raw sessions and never writes to the vault.