Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ovidiu-eremia/mind-memnpx agentmods add skills/ovidiu-eremia/mind-mem/integrity-scanWrote 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/ovidiu-eremia/mind-mem/integrity-scan)<a href="https://agentmods.dev/skills/ovidiu-eremia/mind-mem/integrity-scan"><img src="https://agentmods.dev/badge/skills/ovidiu-eremia/mind-mem/integrity-scan/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/ovidiu-eremia/mind-mem/integrity-scan"><img src="https://agentmods.dev/badge/skills/ovidiu-eremia/mind-mem/integrity-scan.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.00000 | $0.00345 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
integrity-scan 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 9d 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.
This is a copy
100% identical to integrity-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/scan — Memory Integrity Scan
Run the intelligence scanner to detect contradictions, drift, dead decisions, and missing cross-references across the entire memory workspace.
When to Use
- After a session with significant decisions or changes
- During weekly maintenance
- When something "feels wrong" about the memory state
- Before making architectural decisions (verify no contradictions)
How to Run
python3 maintenance/intel_scan.py "${MIND_MEM_WORKSPACE:-.}"
What It Checks
- Contradictions — Decisions that conflict with each other (via ConstraintSignatures)
- Drift — Decisions referenced in daily logs but never formalized
- Dead decisions — Active decisions with no recent references
- Orphan tasks — Tasks referencing non-existent decisions
- Impact graph — Downstream effects of each decision
- Coverage — How many files are monitored vs total
Output
- Updates
intelligence/CONTRADICTIONS.md,intelligence/DRIFT.md,intelligence/IMPACT.md - Updates
memory/intel-state.jsonwith latest metrics and counters - Saves state snapshot in
intelligence/state/snapshots/ - Generates
intelligence/BRIEFINGS.mdweekly briefing
Modes
detect_only— Report issues, never propose changes (default)propose— Report issues AND generate fix proposals inintelligence/proposed/
Check current mode: cat memory/intel-state.json | python3 -c "import json,sys;print(json.load(sys.stdin)['governance_mode'])"
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.
- 9d ago First seen · 36 lines · 0 tokens per session scan A e077911a3fdb
integrity-scan is a skill published in the GitHub repository ovidiu-eremia/mind-mem (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 345 tokens. A static security scan graded it A with 0 findings. It is 100% identical to integrity-scan, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.