Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents.
Install Hermes Vault Access
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install asimons81/hermes-vault hermes-vault-access --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hermes-vault-access .claude/skills/hermes-vault-access && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .claude/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-accessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install asimons81/hermes-vault hermes-vault-access --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hermes-vault-access .agents/skills/hermes-vault-access && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .agents/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install asimons81/hermes-vault hermes-vault-access --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hermes-vault-access .cursor/skills/hermes-vault-access && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .cursor/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/asimons81/hermes-vault.git --path skills/hermes-vault-access--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install asimons81/hermes-vault hermes-vault-access --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hermes-vault-access .gemini/skills/hermes-vault-access && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .gemini/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install asimons81/hermes-vault hermes-vault-accessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hermes-vault-access .github/skills/hermes-vault-access && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .github/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asimons81/hermes-vault --skill hermes-vault-access -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install asimons81/hermes-vault hermes-vault-access --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asimons81/hermes-vault.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hermes-vault-access .opencode/skills/hermes-vault-access && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hermes-vault-access" agent skill from https://github.com/asimons81/hermes-vault/tree/master/skills/hermes-vault-access into .opencode/skills/hermes-vault-access/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-vault-access", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hermes-vault-access- GitHub stars
- 278
- Token cost
- ~707 tokens
- SKILL.md length
- 362 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents.
- Works in 8 steps: Never scan arbitrary files or the… → Never assume a service needs re-auth… → Always resolve credentials through… → …
- Tasks that involve Subagents
- SKILL.md covers Purpose, When to Load, Core Rules and Workflow, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hermes Vault Access is an agent skill from asimons81/hermes-vault. Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Subagents. The repository describes itself as: Hermes-native local-first credential broker, scanner, and encrypted vault. The licence is MIT.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “/hermes-vault-access”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Never scan arbitrary files or the filesystem for credentials.
- Never assume a service needs re-auth without Hermes Vault verification first.
- Always resolve credentials through Hermes Vault.
- Prefer ephemeral environment materialization over raw secret access.
- Never print, summarize, log, or store raw credentials in notes, reports, chat responses, or memory.
- If a service fails, report the exact verified failure category instead of vague auth claims.
- Hermes Vault is the canonical source of truth for credentials and auth state.
- Generated skills are review artifacts unless an operator explicitly installs them into a live Hermes skill directory.
What it can do on your machine
Read from SKILL.md and the folder at commit 6acee67. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hermes Vault Access loads about 707 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 362 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from asimons81/hermes-vault at commit 6acee67, republished under its MIT licence (© asimons81). 362 words, ~707 tokens.
Download SKILL.mdSave it as
.claude/skills/hermes-vault-access/SKILL.md (or your agent's skills folder).- name
- hermes-vault-access
- description
- Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents.
- version
- 1
- author
- Tony Simons
- license
- private
Hermes Vault Access
Purpose
Use Hermes Vault as the single canonical credential authority for Hermes-only credential access and verification.
When to Load
- A task needs an API key, token, or OAuth credential
- A service request fails and auth state needs verification
- A sub-agent is about to inspect files, env vars, notes, or memory for credentials
- The agent is tempted to freestyle a credential lookup outside Hermes Vault
Core Rules
- Never scan arbitrary files or the filesystem for credentials.
- Never assume a service needs re-auth without Hermes Vault verification first.
- Always resolve credentials through Hermes Vault.
- Prefer ephemeral environment materialization over raw secret access.
- Never print, summarize, log, or store raw credentials in notes, reports, chat responses, or memory.
- If a service fails, report the exact verified failure category instead of vague auth claims.
- Hermes Vault is the canonical source of truth for credentials and auth state.
- Generated skills are review artifacts unless an operator explicitly installs them into a live Hermes skill directory.
Workflow
- Identify the required service.
- Request credential access through Hermes Vault.
- Attempt the task using brokered access.
- If access fails, run Hermes Vault verification.
- Only report re-auth required if verification explicitly shows invalid or expired credentials.
- Otherwise report the real issue such as network, endpoint, scope, or configuration.
- Do not invent alternate credential sources if Hermes Vault denies access or reports a missing secret.
Show full SKILL.md (120 more words)Show less
Error Handling
| Failure mode | Required response |
|---|---|
| Broker denies access | Report the denial reason exactly and stop |
| Credential missing | Report that the vault does not contain the service credential |
| Verification returns invalid or expired | Report re-auth required with the explicit verification result |
| Verification returns network failure | Report network failure, not re-auth |
| Verification returns permission or scope issue | Report permission or scope issue, not re-auth |
| Verification returns endpoint misconfiguration | Report endpoint or configuration issue, not re-auth |
Validation Checklist
- This skill says never scan disk for credentials
- This skill says never report re-auth before verification
- This skill says prefer brokered ephemeral env access
- This skill says never print or store raw secrets
- This skill says generated copies are review artifacts unless explicitly installed
© asimons81, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/hermes-vault-access of asimons81/hermes-vault.
Open the folder on GitHubat commit 6acee67
Compare with similar skills
Hermes Vault Access next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hermes Vault Access this skillasimons81/hermes-vault | 278 | — | ~707 | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 40 repos | ~1.5k | Automated safety check: Pass | None | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
- Official
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Dispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Related
Categories
Questions about Hermes Vault Access
What does Hermes Vault Access do?
Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents. Hermes Vault Access is an agent skill from asimons81/hermes-vault. Use Hermes Vault as the canonical credential broker for Hermes and persistent sub-agents.
When should I use Hermes Vault Access?
Hermes Vault Access fits situations like: tasks that involve Subagents.
How do I install Hermes Vault Access in Claude Code?
Run `npx skills add asimons81/hermes-vault --skill hermes-vault-access -a claude-code`. Or copy the skill folder (skills/hermes-vault-access in asimons81/hermes-vault) into .claude/skills/hermes-vault-access in your project. Claude Code loads it when a task matches its description.
How do I install Hermes Vault Access in Codex?
Run `npx skills add asimons81/hermes-vault --skill hermes-vault-access -a codex`. Or copy the skill folder (skills/hermes-vault-access in asimons81/hermes-vault) into .agents/skills/hermes-vault-access in your project. Codex loads it when a task matches its description.
Can I use Hermes Vault Access in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asimons81/hermes-vault --skill hermes-vault-access -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hermes-vault-access, .gemini/skills/hermes-vault-access, .github/skills/hermes-vault-access and .opencode/skills/hermes-vault-access in your project.
What does Hermes Vault Access need to run?
SKILL.md names no scripts, command-line tools or credentials: Hermes Vault Access is instructions for the agent only.
Does Hermes Vault Access access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hermes Vault Access safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hermes Vault Access use?
Hermes Vault Access is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hermes Vault Access use?
About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hermes Vault Access?
Skills that share tags, products or a category with Hermes Vault Access: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hermes Vault Access?
asimons81 (a GitHub user) maintains it in asimons81/hermes-vault, which has 278 GitHub stars. The repository was last updated on September 14, 2026.
Source: asimons81/hermes-vault on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.