Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add asimons81/hermes-vault --skill hermes-vault-accessgit clone --depth 1 https://github.com/asimons81/hermes-vaultWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/asimons81/hermes-vault/hermes-vault-access)<a href="https://agentmods.dev/skills/asimons81/hermes-vault/hermes-vault-access"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-vault/hermes-vault-access/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/asimons81/hermes-vault/hermes-vault-access"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-vault/hermes-vault-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00557 |
| Opus 5 | $0.00011 | $0.00279 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
hermes-vault-access scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
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 |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 63 lines · 22 tokens per session scan A de300af88abd
hermes-vault-access is a skill published in the GitHub repository asimons81/hermes-vault (262 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…