memory-security

Name: memory-security
Availability: InStock
Author: Akshay

Audit memory write, retrieval, and retention paths to prevent cross-session leakage.

4|Updated Apr 27, 2026

Search Tags:#prompt-injection #retention-policy #memory-poisoning #memory-security #scoped-retrieval #deletion-workflow

Ready to run

npx skills add https://github.com/maruakshay/mii-ai-security --skill memory-security

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-security
Source: https://github.com/maruakshay/mii-ai-security/tree/main/skills/memory-security
Command: npx skills add https://github.com/maruakshay/mii-ai-security --skill memory-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses persistent memory poisoning and unsafe long-term memory writes, preventing cross-session influence and stale memory from compromising model behavior.

Core Features & Use Cases

Memory write validation and provenance tagging to block instruction-bearing or sensitive data from being stored
Scoped memory reads to ensure per-user/session isolation and prevent cross-tenant leakage
Deletion, reindexing, and audit trails to ensure memory can be purged and evidence preserved for incident response

Quick Start

Audit your memory write path and implement a deterministic write gate to reject unvalidated memory candidates.

Frequently Asked Questions about memory-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent memory poisoning in persistent AI memory across sessions?▼

To prevent memory poisoning across sessions, implement a deterministic write gate to reject unvalidated memory candidates and apply provenance tagging to block instruction-bearing or sensitive data from being stored in persistent memory architectures.

What is cross-session memory leakage and how does scoped retrieval prevent it?▼

Cross-session memory leakage occurs when isolated data bleeds between tenants. Scoped retrieval prevents this by applying strict per-user and per-session memory read filters, ensuring isolation and stopping cross-tenant data access during retrieval operations.

How do I implement a secure deletion workflow for AI agent memory?▼

Implement a secure deletion workflow by establishing memory purging, reindexing, and audit trail mechanisms. This ensures memory can be safely deleted while evidence is preserved for incident response and compliance tracking.

How do I validate memory writes to block prompt injection in AI systems?▼

Validate memory writes by applying a deterministic write gate that audits memory write paths and rejects unvalidated candidates. Provenance tagging ensures instruction-bearing data from prompt injection attempts is blocked from persistent storage.

Do I need retention policies for per-user memory scoping in multi-agent architectures?▼

Yes, retention policies are essential for per-user memory scoping in multi-agent architectures. They define memory lifecycles, enforce isolation, and prevent stale memory from compromising model behavior across persistent sessions and agents.

Why does stale memory compromise model behavior in persistent AI architectures?▼

Stale memory compromises model behavior because outdated persistent data creates unsafe long-term memory writes. Without retention policies and strict deletion workflows, cross-session influence from stale memory degrades model performance and reliability.