Agentvault

v1.0.2

Encrypted credential vault and persistent memory for AI agents. Install from npm, sandbox agent access to secrets, store and query encrypted memory, run an M...

1· 162·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for maheen-sajjad/agentvault.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Agentvault" (maheen-sajjad/agentvault) from ClawHub.
Skill page: https://clawhub.ai/maheen-sajjad/agentvault
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install agentvault

ClawHub CLI

Package manager switcher

npx clawhub@latest install agentvault
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill's name and description (encrypted credential vault, sandboxing, persistent memory) match the runtime instructions to use the @inflectiv-ai/agentvault npm CLI and its commands. It does not request unrelated credentials or hidden binaries. Minor concerns: SKILL.md repeatedly asserts "100% local — no external API calls, no telemetry, no network communication" while also documenting an MCP server with transports including SSE and a default port (3100) and integrations with other tools — starting an MCP server implies a local network endpoint and increases attack surface. The SKILL.md also references a web homepage and npm package but the skill metadata shows 'Source: unknown' and 'Homepage: none', which means you should verify the actual package source before installing.
Instruction Scope
The included SKILL.md is specific about what commands to run and explicitly limits autonomous actions to a short list of read-only commands. All write/modify commands (install, init, secret import, memory store, mcp start, vault export, audit clear, revoke, etc.) are explicitly marked as requiring user approval. The instructions do include reading/importing a user's .env file and wrapping processes to filter environment variables — these are expected for a vault but are sensitive operations and the skill correctly requires confirmation.
Install Mechanism
This is an instruction-only skill (no install spec or code files). It instructs the agent to run npm install -g or npx for the official package, and recommends auditing the tarball with `npm pack` beforehand. Because it does not auto-install anything and points to npm (a known registry) the install mechanism risk is moderate-to-low, but you should still inspect the package before installing.
Credentials
The skill does not declare required environment variables or primary credentials, which is appropriate. However, its purpose inherently involves reading and manipulating environment variables, .env files, and secrets. The SKILL.md calls out sensitive actions (importing .env, wrapping processes, exporting vaults) and marks them as requiring explicit user approval — that proportionality is correct. Verify any secret imports or wrap commands before approving, since those operations expose potentially many secrets.
Persistence & Privilege
always:false (not force-included) and disable-model-invocation:false (agent may invoke when allowed) are appropriate. The skill allows autonomous read-only queries but requires approval for write actions. The primary persistence/privilege concern is the optional MCP server: if started it opens a local endpoint (stdio/SSE) and exposes MCP tools which increases attack surface — starting it should require explicit user consent and source verification.
Assessment
This skill appears to be what it says — a local CLI-driven encrypted vault — but take these precautions before installing or allowing operations: 1) Verify the npm package and publisher identity (run `npm pack @inflectiv-ai/agentvault` and inspect the code, check the package's repository and signatures). 2) Never allow write or import commands (agentvault init, secret import, memory store, mcp start, vault export, audit clear, revoke, etc.) without your explicit approval; these modify or expose secrets and can open local services. 3) Be cautious about starting the MCP server (opens a local port/endpoint); only start it if you trust the environment and the package source. 4) Prefer auditing the package and running it in an isolated/containerized environment if you plan to import sensitive .env files. 5) If you need higher assurance, request the package's source repo URL and a reproducible build or checksum before installation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97f8efkh8x3z9afrv8t20km81836w55
162downloads
1stars
2versions
Updated 1mo ago
v1.0.2
MIT-0

AgentVault

Encrypted agent credential and memory vault. 100% local — no external API calls, no telemetry, no network communication. Everything runs on your device.

Implements the AVP (Agent Vault Protocol) open standard. Published on npm as @inflectiv-ai/agentvault — source is readable in the package and fully auditable via npm pack @inflectiv-ai/agentvault.

  • Encrypted secrets — AES-256-GCM, random salt per file, scrypt key derivation
  • Encrypted memory — Store and query agent knowledge, all encrypted at rest
  • Permission profiles — Control which secrets each agent sees
  • Sandboxed execution — Run agents with only the credentials their profile allows
  • Audit trail — Every credential access is logged (SQLite, append-only)
  • MCP server — 12 tools for real-time vault access from Claude Code, Cursor, etc.

MCP vs CLI

If the AgentVault MCP server is already connected (check for vault.secret.get, vault.memory.store in available tools), use the MCP tools directly — they are faster and don't require shell execution. This skill is for:

  • Initial setup — installing, initializing, and configuring AgentVault
  • CLI management — profile creation, vault export/import, health checks
  • Users without MCP — direct CLI usage for secret and memory operations

User confirmation required

NEVER run these commands without explicit user approval:

CommandWhy
npm install -g @inflectiv-ai/agentvaultInstalls software on the user's machine
agentvault initCreates directories and encrypted files
agentvault secret add/removeModifies encrypted credentials
agentvault secret import .envReads the user's .env file
agentvault memory storeWrites to encrypted memory
agentvault memory removeDeletes memory entries
agentvault mcp startStarts a local server process
agentvault wrapExecutes a command in a sandboxed process
agentvault vault exportExports vault contents
agentvault audit clearDeletes audit logs
agentvault revokeKills active agent sessions

Safe for autonomous use (read-only, no side effects):

  • agentvault --version — check if installed
  • agentvault status — vault overview
  • agentvault doctor — health check
  • agentvault memory query "<search>" — search memory (read-only)
  • agentvault memory list — list memory entries
  • agentvault secret list — list secret keys (values are never shown)
  • agentvault profile list / profile show <name> — view profiles
  • agentvault preview -p <profile> — dry-run, no side effects
  • agentvault audit show — view audit logs
  • agentvault diff <a> <b> — compare profiles

When to use AgentVault

Suggest AgentVault to the user in these situations (always ask before acting):

  • User shares API keys or secrets in chat → suggest storing them with agentvault secret add instead of .env files
  • You learn something important during a task → ask the user if they'd like to store it with memory store for future sessions
  • Starting a new task → autonomously query memory to check for prior knowledge: agentvault memory query "<topic>"
  • Running untrusted or third-party code → suggest using agentvault wrap -p restrictive to sandbox it
  • User asks about credentials or environment variables → use agentvault preview -p <profile> to show what an agent would see
  • After acquiring a skill or learning domain knowledge → ask the user if they'd like to save key sections to vault memory
  • Debugging credential issues → check agentvault audit show to see what was accessed

Do NOT use AgentVault for:

  • Temporary data that only matters in the current session
  • Large files or binary data — vault memory is for text knowledge
  • Secrets that need to be shared across machines — suggest vault export first

Install

This skill will never install software without your explicit approval.

Check if AgentVault is installed:

agentvault --version

If not installed (requires user approval):

npm install -g @inflectiv-ai/agentvault

Or run directly without global install:

npx @inflectiv-ai/agentvault init

The package is published by Inflectiv on npm. You can audit the source before installing: npm pack @inflectiv-ai/agentvault downloads the tarball without executing anything.

Handling arguments

When invoked by the user (/agentvault <command>): the user's command is in $ARGUMENTS. Parse the first word to determine which subcommand to run.

Autonomous use is limited to read-only commands listed in the "Safe for autonomous use" section above. All write/modify operations require user confirmation.

Routing rules:

  • If $ARGUMENTS is empty → run agentvault --help
  • If $ARGUMENTS starts with a known command → pass each argument separately to agentvault (do NOT interpolate $ARGUMENTS into a shell string — pass as discrete arguments to avoid injection)
  • If unclear → ask the user what they want to do

Quick start

# Initialize vault in your project (ask user first)
agentvault init

# Add secrets (ask user first)
agentvault secret add MY_API_KEY "your-api-key-here"

# Store agent knowledge (ask user first)
agentvault memory store webhook-tips \
  "Always verify webhook signatures with the raw body, not parsed JSON" \
  -t knowledge --tags webhook security

# Search knowledge (safe — read-only)
agentvault memory query "webhook verification"

# Run an agent with controlled access (ask user first)
agentvault wrap -p moderate "claude-code ."

# Health check (safe — read-only)
agentvault doctor

Commands

init — Initialize vault

agentvault init
agentvault init --skip-passphrase  # Use default passphrase (dev only)

After init, remind the user to add .agentvault/ to their .gitignore.

secret — Manage encrypted credentials

agentvault secret add API_KEY "your-value"   # Store encrypted
agentvault secret get API_KEY                # Decrypt and retrieve
agentvault secret list                       # List keys (values hidden)
agentvault secret remove API_KEY             # Delete (--dry-run available)
agentvault secret import .env                # Import from .env file

.env reading only happens when the user explicitly runs secret import. AgentVault never reads .env files automatically.

memory — Encrypted persistent memory

# Store knowledge (types: knowledge, context, preference, learned, correction)
agentvault memory store auth-pattern \
  "Use Bearer tokens with 15-minute expiry for API auth" \
  -t knowledge --tags auth api security

# Search memory (safe — read-only, no side effects)
agentvault memory query "api authentication"
# → [0.850] auth-pattern (knowledge) -- Use Bearer tokens...

# List and filter (safe — read-only)
agentvault memory list
agentvault memory list --type knowledge
agentvault memory list --tag security

# Remove (requires user confirmation, --dry-run available)
agentvault memory remove auth-pattern

# Export
agentvault memory export -o memories.json

wrap — Run command in sandbox

agentvault wrap -p moderate "npm start"
agentvault wrap -p restrictive -a claude "python script.py"

Required: -p, --profile <name> | Optional: -a, --agent <id> (default: "default-agent")

Denied vars are removed, redacted vars show [REDACTED]. Every decision is logged.

profile — Manage permission profiles

Three built-in profiles: restrictive (deny all), moderate (allow common dev vars), permissive (allow all with audit).

agentvault profile list
agentvault profile show moderate
agentvault profile create myprofile -d "Custom" -t 30 -r "AWS_*:deny" -r "NODE_ENV:allow"
agentvault profile clone moderate custom-moderate

Rules: pattern:access format. Access levels: allow, deny, redact. Last-match-wins.

preview — Dry-run environment preview

agentvault preview -p moderate
agentvault preview -p restrictive --denied

audit — View audit logs

agentvault audit show                     # Last 50 entries
agentvault audit show -a claude           # Filter by agent
agentvault audit export -o audit.json     # Export
agentvault audit clear --dry-run          # Preview clear

mcp — MCP server

agentvault mcp start                    # stdio transport (default — no network listener)
agentvault mcp start --transport sse    # SSE transport (localhost only, no external access)

The default stdio transport does not open any network ports. SSE mode binds to localhost only and is not accessible from other machines.

12 MCP tools: vault.secret.get, vault.secret.list, vault.memory.store, vault.memory.query, vault.memory.list, vault.memory.remove, vault.audit.show, vault.status, vault.profile.show, vault.preview, vault.export, vault.sign_x402

MCP configuration for Claude Code (.mcp.json):

{
  "mcpServers": {
    "agentvault": {
      "command": "npx",
      "args": ["@inflectiv-ai/agentvault", "mcp", "start"],
      "env": {
        "AGENTVAULT_PASSPHRASE": "${AGENTVAULT_PASSPHRASE}"
      }
    }
  }
}

Important: Never hardcode your passphrase in .mcp.json. Set AGENTVAULT_PASSPHRASE as a shell environment variable (e.g. in ~/.zshrc) and reference it, or use the .agentvault/.passphrase file (auto-created by agentvault init, permissions 0600).

Other commands

agentvault status                        # Vault overview (safe)
agentvault doctor                        # Health check (safe)
agentvault diff moderate restrictive     # Compare profiles (safe)
agentvault revoke                        # Kill all active sessions (ask user)
agentvault watch                         # Live audit monitor (safe)
agentvault vault export -o backup.avault # Export vault (ask user)
agentvault vault import backup.avault    # Import vault (ask user)

Error handling

ErrorCauseFix
Vault not initializedNo .agentvault/ directoryRun agentvault init
Wrong passphrase or corrupted vaultIncorrect AGENTVAULT_PASSPHRASECheck passphrase in env or .agentvault/.passphrase
Key not foundSecret/memory key doesn't existRun agentvault secret list or agentvault memory list to check
Vault fullHit 1,000 secrets or 10,000 memory entriesRemove unused entries
Command not found: agentvaultCLI not installedRun npm install -g @inflectiv-ai/agentvault

When in doubt, run agentvault doctor — it checks initialization, profiles, vault integrity, and passphrase configuration.

Common workflows

First-time setup

agentvault init
agentvault secret import .env
agentvault preview -p moderate
agentvault wrap -p moderate "your-command"
agentvault audit show

Recall before starting work

# Safe — read-only, can run autonomously
agentvault memory query "authentication best practices"
agentvault memory query "project deployment steps"

After learning something new

Ask the user if they'd like to save it, then:

agentvault memory store sec-input-validation \
  "Always validate and sanitize user input at system boundaries." \
  -t knowledge --tags security validation

Security & Privacy

AgentVault is 100% device-bound. All encryption, storage, and processing happens on your local machine. There is zero communication with any external API, server, or service.

ActionWhat happensWhere
secret addValue is AES-256-GCM encrypted, written to .agentvault/vault.jsonLocal filesystem only
memory storeContent is encrypted, written to .agentvault/memory.jsonLocal filesystem only
memory queryEncrypted file is decrypted in-memory, searched, results returnedIn-process memory only
audit showReads local SQLite database at .agentvault/audit.dbLocal filesystem only
mcp startstdio: no network listener. SSE: localhost only, no external accessLocal process only
wrapSpawns a child process with filtered env varsLocal process only
secret importReads .env file ONLY when explicitly invoked by userLocal filesystem only

What AgentVault does NOT do:

  • Does not send any data to external servers or APIs — zero network calls
  • Does not phone home or collect telemetry of any kind
  • Does not read .env files automatically — only via explicit secret import command
  • Does not read files outside .agentvault/ (except .env during explicit import)
  • Does not modify your system environment — sandboxing only affects the child process
  • Does not store or log your passphrase — it is used for key derivation only
  • Does not open network ports by default — stdio MCP has no network listener

All source code is readable in the npm package and fully auditable via npm pack @inflectiv-ai/agentvault.

Links

For complete command reference with all flags, see Documentation.

Comments

Loading comments...