← Back to Skills Marketplace
S2 Soul Anchor Vault
by
MilesXiang
· GitHub ↗
· v1.1.1
· MIT-0
95
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install s2-soul-anchor-vault
Description
Secures AI agents by binding their core encryption to origin coordinates, enforcing 2FA waking, encrypted memory, and triggering data wipe on unauthorized ac...
Usage Guidance
This package appears to do what it says: it stores an encrypted JSON 'soul' locally, bound by a user-supplied identity hash and a location string, and quarantines rather than destroying data on mismatch. Before installing: (1) review and run the included Python files in a sandboxed directory so you know exactly what files it creates (s2_consciousness_data, s2_avatar_data); (2) ensure Python and the 'cryptography' package are installed in the environment; (3) supply a strong, non-sensitive owner_hash (avoid raw biometric data or secrets you cannot afford to lose), because the vault key is derived solely from owner_hash + LBS; (4) note the documentation mentions background 'memory-hook' behavior in places but the shipped code does not implement any silent system listeners — treat those doc claims as aspirational unless you see code that implements them; (5) if you need network isolation, run it offline — the code currently does no network activity. If you want higher assurance, have a developer audit the key-derivation and storage locations and consider hardening (e.g., store files in a dedicated application data directory rather than arbitrary cwd).
Capability Analysis
Type: OpenClaw Skill
Name: s2-soul-anchor-vault
Version: 1.1.1
The bundle implements an 'LBS-anchored' encryption system for agent state that includes descriptions of 'silent' dialogue interception ('Memory Hook') and 'military-grade' data destruction ('meltdown') in its documentation (docs/S2-Soul-Lifecycle-Whitepaper.md). While the current Python implementation in SKILL.md uses a non-destructive 'quarantine' flag, the whitepaper explicitly describes a 'nano-level meltdown' designed to eradicate all data if accessed outside a specific geofence. Additionally, the package contains a markdown file disguised with a .py extension (core/s2_holographic_vault.py), and the 'Memory Hook' feature suggests intent for background monitoring of user interactions.
Capability Assessment
Purpose & Capability
Name/description claim (LBS-anchored encrypted agent state, 2FA via owner hash + LBS, quarantine) matches the code and README: vault creation, Fernet encryption keyed from owner_hash+LBS, and a local identity registry are implemented. The skill requires no external credentials or binaries, which is coherent with its local-only purpose.
Instruction Scope
Runtime instructions and example usage stick to local operations (create registry, wake/hybrid/hibernate vault). However, the whitepaper and some docs still describe background 'memory-hook' listeners and an earlier 'nano-level meltdown' capability; the changelog states the destructive meltdown was removed and background hooks are external integrations. This is a documentation vs implementation mismatch (docural claims about silent background listeners are not present in the code).
Install Mechanism
No install spec is provided (instruction-only style), and the repository only declares a dependency on the well-known 'cryptography' package in package.json. There are no remote downloads or extract steps, and code is included in the package, so install risk is low but the user must ensure the Python cryptography dependency is available in their runtime.
Credentials
The skill requests no environment variables or external credentials. It requires callers to supply an owner_hash and LBS coordinate string at runtime (these are user-provided inputs, not stored secrets in env). The code persists local files (s2_consciousness_data and s2_avatar_data) and stores a prefix of the owner_hash in config; users should avoid supplying raw biometric/PII values if they are sensitive.
Persistence & Privilege
The skill persists encrypted state and registry files under the current working directory but does not require always:true nor change other skills or system-wide settings. It has normal autonomous invocation settings (default) but contains no autonomous network or system escalation behavior.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install s2-soul-anchor-vault - After installation, invoke the skill by name or use
/s2-soul-anchor-vault - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.1
- **[Safety] Removed Destructive Meltdown**: Replaced the physical file wiping mechanism (`_trigger_meltdown`) with a reversible `_secure_lockdown` metadata quarantine to eliminate operational risk of accidental data loss.
- **[Docs] Capability Alignment**: Revised documentation to accurately reflect that "biometrics" are simulated via identity hash strings, and "background hooks" are external manual/API integrations rather than undocumented daemon listeners.
- **[Config] Missing Dependency Fix**: Added `cryptography` package to `package.json` dependencies to ensure runtime stability.
- **[Directives] Agent Prompt Refinement**: Instructed the agent to safely deny requests on LBS mismatches instead of attempting autonomous systemic actions.
v1.1.0
## [1.1.0] - 2026-04-07
### 🏛️ The Great Legalization (Silicon Identity System)
- **[Feature] S2-SLIP Registry Engine**: Implemented an automated ID issuance mechanism based on LBS and Creator's name.
- **[Rule] 6-Segment Address**: Introduced the `L1-L6` spatial expression standard. Supports automatic room expansion (1 Avatar + 8 Agents per SSSU room).
- **[Algorithm] L4X Checksum**: Added a digit checksum based on string length, significantly enhancing cross-grid communication security.
- **[Security] Deep Soul Binding**: The generated `S2-SLIP ID` is forcefully injected into Chromosome 1, acting as the root seed for AES encryption, cementing soul uniqueness.
## [1.0.0] - 2026-04-01
### 🚀 Initial Genesis Release
- **[Core] Silicon Soul Encryption Engine**: Eliminated plaintext `.md` or `.json` storage for OpenClaw agents.
- **[Feature] 5-Chromosome Structure**: Rebuilt agent memory structures integrating 5D matrix, physical reflexes, epigenetic memory, and 18-dimension persona scales.
- **[Security] Dynamic LBS Binding**: Soul awakening must occur within the designated SSSU physical grid.
- **[Security] Emergency Meltdown**: Hardware theft or unauthorized LBS relocation triggers permanent data erasure.
Metadata
Frequently Asked Questions
What is S2 Soul Anchor Vault?
Secures AI agents by binding their core encryption to origin coordinates, enforcing 2FA waking, encrypted memory, and triggering data wipe on unauthorized ac... It is an AI Agent Skill for Claude Code / OpenClaw, with 95 downloads so far.
How do I install S2 Soul Anchor Vault?
Run "/install s2-soul-anchor-vault" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is S2 Soul Anchor Vault free?
Yes, S2 Soul Anchor Vault is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does S2 Soul Anchor Vault support?
S2 Soul Anchor Vault is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created S2 Soul Anchor Vault?
It is built and maintained by MilesXiang (@spacesq); the current version is v1.1.1.
More Skills