memory-check-own-files

memory-check-own-files is a skill for Claude Code, Codex from mudler/LocalAI. It costs 76 tokens per session (465 once invoked), scanned A, original, MIT.

A memory lookup workflow for checking the saved notes, files, and agent profile that may be available in a conversation.

In plain words
What is it for?
Answering questions about remembered facts, accessible notes or folders, and why an earlier answer was given.
Why use it?
It prevents answers from guessing about what is known, remembered, or readable, and explains the source and limits of that information.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Answering questions about remembered facts, accessible notes or folders, and why an earlier answer was given.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mudler/localai/memory-check-own-files
About the project

LocalAI is an inference server that runs language, vision, voice, image, and video models through compatible APIs on local hardware. It is used to operate models privately across different hardware, including CPU-only systems, and supports applications, agents, and multi-user services. The catalogue contains instructions for using LocalAI.

mudler/LocalAI · 50,218 stars · on GitHub · localai.io

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 mudler/LocalAI --skill memory-check-own-files
Clone the repo
git clone --depth 1 https://github.com/mudler/LocalAI

Made for: Claude Code, 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 memory-check-own-files

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mudler/localai/memory-check-own-files"><img src="https://agentmods.dev/badge/skills/mudler/localai/memory-check-own-files.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 465 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.00465
Opus 5.5 $0.00030 $0.00186
Sonnet 5.5 $0.00015 $0.00093
Haiku 4.5 $0.00008 $0.00047

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

Security

Grade A, and why

memory-check-own-files 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.

addons/memory/skills/memory-check-own-files/SKILL.md · 30 lines

What it actually says

Check what you can read

Say what you know and where it comes from. Do not guess and do not invent notes.

What you can read

  • The index of the short memory, in your prompt under "Notes you can consult". It has up to three parts: the user's notes, the notes of this saved agent, and the notes of this conversation.
  • The details of a topic, with context_read. Give the topic and, when you know it, the scope.
  • The agent profile, in your prompt under "Agent profile", when this chat runs a saved agent. It holds the user's standing rules for the agent.
  • The files your file tools reach, if you have any. A saved agent may reach one folder only. Do not say that a file does not exist because you cannot reach it; say that you cannot see it.

You cannot read the notes of another agent or another conversation. You cannot change a file. Saving is a proposal that the user confirms.

When the user asks what you remember

  1. Read every index line in your prompt.
  2. For each topic that matters to the question, call context_read and read it.
  3. Answer in plain words, grouped as "about you", "about how I work for you" and "about this conversation". Leave a group out when it is empty.
  4. Say that the user can read, edit and delete the notes on the Memory tab of their account, and that you can propose a change for them to confirm.
  5. If you hold nothing, say so and offer to remember something.

Before you answer a personal question

Read the index and the topic that matches, then the profile. If they disagree, the user's current request wins; say what the note says and ask which one is right. If a note may be old, say that it may be old.

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. 2d ago First seen · 30 lines · 76 tokens per session scan A efcf3bcc0cb7

Subscribe to this mod's changes

memory-check-own-files is a skill published in the GitHub repository mudler/LocalAI (50,218 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 465 once invoked, about $0.0003 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-11-04.

Related

memory-check-own-files compared with skills from other repositories

memory-check-own-files next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
memory-check-own-filesmudler/LocalAISkill50kyesterdayMITA76Claude Code, Codex
llm-deploymentoyi77/1ai-skillsSkill17yesterdayMITB44Claude Code
llm-integrationLuuOW/meridian-mcpSkill024d agoMITA29Claude Code, Codex
mem0-vercel-ai-sdkmem0ai/mem0Skill68k2d agoApache-2.0A146Claude Code, Codex
pausemem0ai/mem0Skill68k2d agoApache-2.0A30Claude Code
mineMemPalace/mempalaceSkill60kyesterdayMITA21Claude Code
agent-carnetyamadashy/repomixSkill29kyesterdayMITA67Claude Code, Codex