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 samrusani/AliceMemory --skill alice-explain-provenancegit clone --depth 1 https://github.com/samrusani/AliceMemoryWrote 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/samrusani/alicememory/alice-explain-provenance)<a href="https://agentmods.dev/skills/samrusani/alicememory/alice-explain-provenance"><img src="https://agentmods.dev/badge/skills/samrusani/alicememory/alice-explain-provenance/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/samrusani/alicememory/alice-explain-provenance"><img src="https://agentmods.dev/badge/skills/samrusani/alicememory/alice-explain-provenance.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00464 |
| Opus 5.5 | $0.00010 | $0.00186 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
alice-explain-provenance 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.
What it actually says
Alice Explain Provenance
Legacy pack. The supported Hermes pack is agent-skills/hermes/alice-memory.
This skill needs the full tool surface: set ALICE_MCP_FULL_TOOLS=1 in the
Alice MCP server env. On the default three tools, only the alice_recall step
works.
Goal
Provide evidence-backed explanations for Alice-based answers.
Trigger Cues
Use this skill when the user asks:
- why are you saying this
- what source supports this
- can you show evidence or provenance
Required MCP Tools
mcp_<alice_server>_alice_context_pack- Optional:
mcp_<alice_server>_alice_recall
<alice_server> is the key under mcp_servers. It is alice when
alice-memory install --host hermes wrote it and alice_core in the example
configs.
Workflow
- Start from
alice_context_packwith the claim asquery. It takes nothread_id. - If needed, run a focused
alice_recallquery for missing evidence. - Explain answer claims by citing returned continuity object IDs and provenance fields.
- If provenance is thin, state uncertainty and propose the next validating step.
Tool Call Templates
mcp_<alice_server>_alice_context_pack({"query":"<claim>","include_sources":true,"max_items":10})
mcp_<alice_server>_alice_recall({"thread_id":"<uuid>","query":"<claim>","limit":5})
Output Contract
Always include:
- claim
- supporting object IDs
- provenance summary from returned records
- confidence posture (
high,medium,low) based on evidence quality
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 Changed · +7 lines 4ff9594f52df
- 1mo ago First seen · 57 lines · 26 tokens per session scan A b4bcb6fa1860
alice-explain-provenance is a skill published in the GitHub repository samrusani/AliceMemory (4 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 464 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-31.
Other skills, from other repositories
plur-create-engrams
Create or improve PLUR engrams from conversations, documents, decisions, observations, and explicit preferences. Use for memory extraction, engram authoring, or reviewing proposed memories, including global, scoped, pinned, retrieved, and provisional knowledge. Ordinary use of existing memories does not require this…
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.
remnic-memory-workflow
Shared memory workflow for Claude Code agents connected to Remnic — recall before acting, observe during work, remember at the end. Trigger phrases include "what do you remember about", "save this for later", "any context from last time".
remnic-remember
Store a durable memory in Remnic so every connected agent can recall it. Trigger phrases include "remember this", "save this for later", "add a note that".