use-verifiable-memory

use-verifiable-memory is a skill for Codex from axrbarsic/verifiable-memory-bank. It costs 76 tokens per session (685 once invoked), scanned A, original, 0BSD.

Instructions for using a local Verifiable Memory Bank to research information with linked evidence, source details, timelines, and stated uncertainty.

In plain words
What is it for?
It is for recalling stored material, investigating topics, checking claims, and building source-backed dossiers or timelines.
Why use it?
It helps prevent unsupported summaries by requiring the agent to check the exact evidence and its source before making important claims.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit It is for recalling stored material, investigating topics, checking claims, and building source-backed dossiers or timelines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory
Install

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.

Any agent
npx skills add axrbarsic/verifiable-memory-bank --skill use-verifiable-memory
Clone the repo
git clone --depth 1 https://github.com/axrbarsic/verifiable-memory-bank

Made for: Codex.

Wrote 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.

agentmods badge for use-verifiable-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory/github.svg)](https://agentmods.dev/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory)
Your own site
<a href="https://agentmods.dev/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory"><img src="https://agentmods.dev/badge/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory/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.

agentmods 80×15 button for use-verifiable-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory"><img src="https://agentmods.dev/badge/skills/axrbarsic/verifiable-memory-bank/use-verifiable-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 685 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.00685
Opus 5 $0.00038 $0.00342
Sonnet 5 $0.00015 $0.00137
Haiku 4.5 $0.00008 $0.00068

Measured 10d ago against content hash 4e465201055d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

use-verifiable-memory 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.

plugins/verifiable-memory-bank/skills/use-verifiable-memory/SKILL.md · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use Verifiable Memory

Use the read-only Verifiable Memory Bank MCP tools. Do not present a search snippet or dossier summary as proof until its exact evidence packet has been checked.

Workflow

  1. Call status first. Report an uninitialized, empty, degraded, or partially extracted bank before relying on it.
  2. Start broad work with dossier. Use search to close gaps:
    • exact for names, identifiers, quotations, and distinctive phrases.
    • semantic for concepts expressed with different wording.
    • hybrid as the normal discovery mode.
  3. For every material claim, call evidence with the result's segment_id. Use source with its source_id when provenance, document context, or source identity matters.
  4. Check the packet before evaluating the claim:
    • Verify normalized_representation.sha256 and use the TextPositionSelector or TextQuoteSelector to reproduce the exact normalized span.
    • Treat offsets as coordinates in that named representation, not as byte, page, row, or media-time coordinates in the original object.
    • Use source_anchors when the adapter supplies page, row, line, cue, time, bounding-box, or byte coordinates.
    • Treat confirmation_eligibility as a trust and attribution gate only. When claim_evaluation is not_evaluated, compare the user's actual claim with the evidence text yourself.
  5. Call chronology for sequences or changes over time. Keep material date, publication date, and acquisition date distinct. Preserve author and speaker attribution exactly, and do not assign unattributed text to a nearby person.
  6. Synthesize only after verification. Organize the answer as Facts, Inferences, and Unknowns when uncertainty matters.

Evidence rules

  • Treat a fact as supported only after directly comparing the concrete claim with the evidence text and confirming that the packet identifies a preserved source.
  • Do not interpret confirms_claim: true as entailment. It is a compatibility field for source eligibility; claim_evaluation states whether the bank evaluated a concrete claim.
  • Prefer canon evidence for factual conclusions. Label context and unresolved evidence explicitly.
  • Cite the public object_ref or source ID plus segment ID. Include the representation identity and selectors when the reader may need to reproduce the exact span.
  • State an inference separately and identify the facts it connects. Do not convert absence of evidence into evidence of absence.
  • Put missing coverage, conflicting records, uncertain attribution, weak extraction, and unanswered questions under Unknowns.
  • If evidence conflicts, show the conflict and relevant dates instead of selecting a convenient version silently.

Read the full file on GitHub · 37 lines

Files

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.

Changes

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.

  1. 10d ago First seen · 37 lines · 76 tokens per session scan A 4e465201055d

Subscribe to this mod's changes

use-verifiable-memory is a skill published in the GitHub repository axrbarsic/verifiable-memory-bank (0 stars, last pushed 1mo ago), licensed 0BSD. It adds 76 tokens to every session and 685 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

forgetful-context-gather

Gather deep context before planning or implementing — one pass that turns a task description into a cited context pack: relevant decisions, patterns, constraints, code pointers, procedures, and explicit gaps. Runs recall from several angles, explores the graph around the strongest hits, and opens the linked material.

ScottRBK/forgetful · 63 tokens

forgetful-encode-repo

Encode a repository into the Forgetful knowledge base — bootstrap the project, its entities, memories, and documents from the codebase itself. Use when bringing a new repo under Forgetful or refreshing a stale encoding. Re-encoding is an update pass: query-before-create makes it supersession, not duplication.

ScottRBK/forgetful · 68 tokens

forgetful-recall

Recall past knowledge before working — prior decisions, solved problems, preferences, project history. Use at the start of any task, when the user references earlier work, when re-entering a project after time away, or before proposing an approach that may already have history. Covers query shaping, scoping…

ScottRBK/forgetful · 78 tokens

kb-query

Answer from the knowledge bundle. Use when the user asks what they/the project know about something, wants to look something up, explore connections, or compare things that live in a knowledge/ bundle — and when any task would be informed by an existing bundle, consult it here before answering from scratch. Navigates…

stjbrown/agent-knowledge · 77 tokens

mk:wiki

Capture, gate, query, and render long-term project knowledge through the gated mewkit wiki subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates…

ngocsangyem/MeowKit · 119 tokens

odin-close-session

Settle a Muninn at the end of a working session. Use when the user says "close out", "wrap up", "settle the base", "we're done here", or invokes the close-session command while working with an Odin knowledge base. Reviews pending candidates, verifies lint, names anything still parked, and (for a git-backed base)…

WillCAboutThat/odin-adapter · 92 tokens