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 flavien-ia/hypervibe-harness --skill _add-keyringgit clone --depth 1 https://github.com/flavien-ia/hypervibe-harnessWrote 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/flavien-ia/hypervibe-harness/_add-keyring)<a href="https://agentmods.dev/skills/flavien-ia/hypervibe-harness/_add-keyring"><img src="https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_add-keyring/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/flavien-ia/hypervibe-harness/_add-keyring"><img src="https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_add-keyring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 73 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00070 | $0.02822 |
| Opus 5 | $0.00035 | $0.01411 |
| Sonnet 5 | $0.00014 | $0.00564 |
| Haiku 4.5 | $0.00007 | $0.00282 |
Grade A, and why
_add-keyring scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `ERROR: ...` → report it to the user and offer the official manual install (https://bitwarden.com/help/cli/), non-blocking. **NEVER improvise a download of `bw`/`bw.exe` yourself** (ad-hoc PowerShell `Invoke-WebRequest How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
_add-keyring - The vault for your access keys
Communication
- Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like
/bootstrapcarries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim. - Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms.
- When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
- Show progress as a short natural-language checklist (in-progress and done states).
You set up an encrypted vault (Bitwarden) where the user's global keys (Cloudflare, Neon, email, etc.) will live - the ones they reuse across all their projects. Instead of sitting in plain text in system variables, they are encrypted and you read them on demand after a daily unlock.
Script vocabulary (internal):
INSTALL="${CLAUDE_SKILL_DIR}/../../scripts/vault/install-bw.mjs",VAULT="${CLAUDE_SKILL_DIR}/../../scripts/vault/vault.mjs",LAUNCH="${CLAUDE_SKILL_DIR}/../../scripts/vault/launch.mjs".
Step 1 - OS detection + tool installation
Detect the OS silently:
uname -s 2>/dev/null || echo "Windows"
Darwin→mac, MINGW/MSYS/Windows→windows, Linux→linux.
Install the Bitwarden tool (idempotent, does nothing if it is already there):
node "${CLAUDE_SKILL_DIR}/../../scripts/vault/install-bw.mjs"
OK→ already present, say nothing.INSTALLED...→ say "I installed the vault tool." The PATH may not be active in the current terminal - for the rest of THIS session, export the bin folder:- Windows:
export PATH="$PATH:$HOME/.hypervibe/bin:/c/Users/$USERNAME/.hypervibe/bin" - mac/linux:
export PATH="$PATH:$HOME/.hypervibe/bin"
- Windows:
ERROR: ...→ report it to the user and offer the official manual install (https://bitwarden.com/help/cli/), non-blocking. NEVER improvise a download ofbw/bw.exeyourself (ad-hoc PowerShellInvoke-WebRequest, directcurl, etc.): running an unscripted external binary triggers an authorization prompt and is not reliable. If you think the install failed for a transient reason (network), re-run the sameinstall-bw.mjsonce; otherwise, route to the official manual install.
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.
- 10d ago First seen · 153 lines · 70 tokens per session scan A 02880bc4f949
_add-keyring is a skill published in the GitHub repository flavien-ia/hypervibe-harness (37 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 2,822 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…