How do I install the Agent Id Vault skill?

Run npx skillmds@latest add tomevault-io/agent-id-vault in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Id Vault safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Id Vault?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Id Vault free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Id Vault?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Id Vault by tomevault-io — Agent Skill

Name: Agent Id Vault
Author: tomevault-io

Agent Id Vault

Encrypted credential vault keyed off the agent's Alien Agent ID private key. Store, retrieve, list, and remove external-service credentials (GitHub PAT, Slack token, AWS keys, etc.) without ever hardcoding secrets. Use when the user asks to save, fetch, or remove a service credential, or whenever a downstream tool needs an external-service secret that should not appear in shell history, source files, or process arguments. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Alien Agent ID — Vault

Encrypted storage for external-service credentials. The encryption key is derived from the agent's main private key via HKDF-SHA256, so credentials are only readable on the same machine as the bound agent. Encryption is AES-256-GCM with a fresh IV per write.

Requires that agent-id-setup bootstrap has already produced a keypair under ${AGENT_ID_STATE_DIR:-$HOME/.agent-id}.

Resolve the CLI

bin/cli.mjs lives in this plugin's directory. Substitute CLI with the absolute path (e.g. node /abs/path/to/plugins/agent-id-vault/bin/cli.mjs) in the examples below.

Store a credential

# Most secure — never appears in argv or shell history:
node CLI store --service github --credential-file /tmp/gh-token

# From an environment variable (typed/pasted into the calling shell):
GH_TOKEN=ghp_... node CLI store --service github --credential-env GH_TOKEN

# Piped via stdin:
echo "$GH_TOKEN" | node CLI store --service github

# Fallback — visible in process list and shell history, avoid:
node CLI store --service github --credential "ghp_..."

Optional flags: --type api-key|oauth|..., --url <hint>, --username <hint>.

Never accept a secret pasted into chat. Transcripts persist. Use a file or env var as the transport.

Retrieve a credential

node CLI get --service github

Returns JSON { ok, service, type, credential, url, username }. Pipe .credential into the calling tool:

GH_TOKEN=$(node CLI get --service github | jq -r .credential)
curl -H "Authorization: Bearer $GH_TOKEN" https://api.github.com/user

List or remove

node CLI list             # metadata only — never returns plaintext credentials
node CLI remove --service github

Common flag

--state-dir <path> — defaults to $AGENT_ID_STATE_DIR then ~/.agent-id.

Source: alien-id/agent-id — distributed by TomeVault.

---name: agent-id-vaultdescription: Encrypted credential vault keyed off the agent's Alien Agent ID private key. Store, retrieve, list, and remove external-service credentials (GitHub PAT, Slack token, AWS keys, etc.) without ever hardcoding secrets. Use when the user asks to save, fetch, or remove a service credential, or whenever a downstream tool needs an external-service secret that should not appear in shell history, source files, or process arguments. Use when this capability is needed.---# Alien Agent ID — VaultEncrypted storage for external-service credentials. The encryption key is derived from the agent's main private key via HKDF-SHA256, so credentials are only readable on the same machine as the bound agent. Encryption is AES-256-GCM with a fresh IV per write.Requires that `agent-id-setup bootstrap` has already produced a keypair under `${AGENT_ID_STATE_DIR:-$HOME/.agent-id}`.## Resolve the CLI`bin/cli.mjs` lives in this plugin's directory. Substitute `CLI` with the absolute path (e.g. `node /abs/path/to/plugins/agent-id-vault/bin/cli.mjs`) in the examples below.## Store a credential```bash# Most secure — never appears in argv or shell history:node CLI store --service github --credential-file /tmp/gh-token# From an environment variable (typed/pasted into the calling shell):GH_TOKEN=ghp_... node CLI store --service github --credential-env GH_TOKEN# Piped via stdin:echo "$GH_TOKEN" | node CLI store --service github# Fallback — visible in process list and shell history, avoid:node CLI store --service github --credential "ghp_..."```Optional flags: `--type api-key|oauth|...`, `--url <hint>`, `--username <hint>`.Never accept a secret pasted into chat. Transcripts persist. Use a file or env var as the transport.## Retrieve a credential```bashnode CLI get --service github```Returns JSON `{ ok, service, type, credential, url, username }`. Pipe `.credential` into the calling tool:```bashGH_TOKEN=$(node CLI get --service github | jq -r .credential)curl -H "Authorization: Bearer $GH_TOKEN" https://api.github.com/user```## List or remove```bashnode CLI list # metadata only — never returns plaintext credentialsnode CLI remove --service github```## Common flag`--state-dir <path>` — defaults to `$AGENT_ID_STATE_DIR` then `~/.agent-id`.---> Source: [alien-id/agent-id](https://github.com/alien-id/agent-id) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions