Legacyshield

Secure, zero-knowledge encrypted vault for agents to store and manage sensitive documents and digital legacy assets.

Install
cmdop skills install agensi-legacyshield

LegacyShield is a skill that provides a zero-knowledge encrypted persistence layer for AI agents. It is designed for workflows where agents need to store and retrieve highly sensitive user data — such as legal documents, identity files, and digital legacy assets — across sessions and platforms, without the agent itself or the storage provider ever accessing the plaintext content. Encryption keys are stated to never leave the agent environment, which is the core of its zero-knowledge security claim.

A key feature is its configurable Dead Man’s Switch logic, which enables automated digital inheritance and succession workflows. This addresses scenarios where agents need to act on behalf of a user under predefined conditions, maintaining high-integrity automation over sensitive assets.

LegacyShield uses a Model Context Protocol (MCP)-compliant interface, making it compatible with MCP-supporting orchestration environments. It is noted as optimized for Claude Code, OpenClaw, and Codex. Because no tool list is exposed, agent interactions with the vault are mediated entirely through the skill’s MCP interface.

This skill is not a general-purpose database or document store — its scope is specifically sensitive, long-lived user data in agentic contexts where privacy guarantees and digital succession matter. Developers working on estate planning automation, cross-session identity management, or sensitive document persistence are the intended audience.

Use cases

  • Store encrypted legal documents that persist across agent sessions without exposing plaintext
  • Implement digital inheritance workflows using the Dead Man's Switch automation logic
  • Share sensitive context between Claude Code, OpenClaw, and Codex agent sessions
  • Persist identity files for long-running agentic pipelines with zero-knowledge guarantees
  • Automate digital succession for user assets under configurable trigger conditions

When to use it

  • When an agent must retain sensitive user documents across sessions without the storage layer seeing plaintext
  • When building digital estate or legacy management workflows that require automated succession logic
  • When the orchestration environment supports MCP and the agent runs in Claude Code, OpenClaw, or Codex
  • When privacy guarantees require that encryption keys never leave the agent environment

When not to use it

  • When the use case is general structured data storage or a relational or document database
  • When the deployment environment does not support MCP-based skill integration
  • When a license, package registry, or auditable open-source supply chain is required, as none are provided in the registry record
  • When enumerated tool definitions are needed at runtime, as the skill exposes no listed tools