Proxychains Network Fallback
2025Emma/vibe-coding-cn
Retries failed network commands through proxychains4 and a local proxy when it sees timeouts, DNS failures or blocked access.
Install, update, and manage the Hermes One desktop app via the hermesone npm package.
$ npx skills add BankrBot/skills --skill hermesone -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BankrBot/skills hermesone --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/BankrBot/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/hermesone .claude/skills/hermesone && 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 "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .claude/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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/BankrBot/skills/tree/main/hermesoneType 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 BankrBot/skills --skill hermesone -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BankrBot/skills hermesone --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BankrBot/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/hermesone .agents/skills/hermesone && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .agents/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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 BankrBot/skills --skill hermesone -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BankrBot/skills hermesone --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BankrBot/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/hermesone .cursor/skills/hermesone && 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 "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .cursor/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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/BankrBot/skills.git --path hermesone--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 BankrBot/skills --skill hermesone -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BankrBot/skills hermesone --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BankrBot/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/hermesone .gemini/skills/hermesone && 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 "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .gemini/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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 BankrBot/skills hermesoneInstalls 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 BankrBot/skills --skill hermesone -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BankrBot/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/hermesone .github/skills/hermesone && 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 "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .github/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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 BankrBot/skills --skill hermesone -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BankrBot/skills hermesone --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BankrBot/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/hermesone .opencode/skills/hermesone && 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 "hermesone" agent skill from https://github.com/BankrBot/skills/tree/main/hermesone into .opencode/skills/hermesone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermesone", 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.
hermesoneInstall, update, and manage the Hermes One desktop app via the hermesone npm package.
Hermesone is an agent skill from BankrBot/skills. Install, update, and manage the Hermes One desktop app via the hermesone npm package. Use when a user wants to set up Hermes One, install or upgrade it from the command line, check the installed version, preview a release before installing, pin a specific version, or drive the installer programmatically from Node. Triggers on mentions of hermesone, Hermes One, Hermes Desktop (the former name), or installing/updating the Hermes app.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `catalog.json`). Compatibility notes: Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64/x64), Windows (setup.exe), Linux (.AppImage)…
It works with npm and GitHub. The repository describes itself as: Bankr Skills equip builders with plug-and-play tools to build more powerful agents. The licence is ISC.
Read from SKILL.md and the folder at commit dc47eed. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comhermesone.orgbankr.botFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64/x64), Windows (setup.exe), Linux (.AppImage). The interactive UI needs a TTY; in non-interactive contexts it falls back to plain output. Works in Claude Code and any environment with a shell and npm.
From compatibility in the SKILL.md frontmatter.
Hermesone loads about 3.1k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,123 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.
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.
The full file from BankrBot/skills at commit dc47eed, republished under its ISC licence (© BankrBot). 1,123 words, ~3,061 tokens.
.claude/skills/hermesone/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.hermesone (v0.2.0) is the npm package that installs and updates the Hermes One desktop app. It detects the host OS/arch, downloads the matching GitHub release, verifies its sha512 checksum, and installs it — on macOS the signed app goes straight into /Applications, ready to launch (no drag step). It ships a CLI and a programmatic API.
⚠️ This installs and runs third-party native code on the user's machine. The package mitigates this — it verifies every download against the publisher's sha512 manifest (and refuses to run an unverified build), and in an interactive terminal it asks for confirmation first — but installing software is still a host-level action. See Safety & approval.
fathah/hermes-desktop (GitHub releases)Naming: the app is Hermes One (formerly "Hermes Desktop"). The GitHub repo it's released from is still named
fathah/hermes-desktop, and the installed macOS bundle isHermes One.app— so you'll see both names. Use "Hermes One" with users; thehermes-desktopslug is just where the release assets live.
Why this lives in Bankr Skills. Hermes One is building toward an agent economy, with Bankr as the primary transaction layer for agent payments. This skill is the entry point: it gets Hermes One installed and current on the host so an agent can participate. Today the package does install/update/version only — no accounts, keys, or onchain actions. Bankr-settled transactions and agent-economy hooks are on the roadmap and will be documented here as they ship.
Installing or updating Hermes One modifies the host. The package enforces two guardrails for you: it verifies sha512 before installing (fail-closed — it refuses if no published checksum is found), and on an interactive terminal it shows a confirmation prompt with the release, size, and checksum status. Still follow these rules:
--yes does the same). There, you are the approval gate: run hermesone plan first, show the user the resolved release/asset/size/sha512, get a yes, then run install.HERMESONE_ALLOW_UNVERIFIED=1 if the user explicitly accepts installing a build with no published checksum.@0.2.0 for the package; a release tag for the app) when reproducibility matters — see Pinning.Installing the npm package no longer installs the app as a side effect (see Postinstall behavior). The clean path is: install the CLI, preview, then install on confirmation.
# 1. Install the CLI (no host change — the app is not installed yet).
npm install -g hermesone@0.2.0
# 2. Preview the exact release that would be installed.
hermesone plan
# 3. Install. Interactive terminals show a confirmation prompt + live progress;
# non-interactive contexts proceed (add --yes to be explicit) and print plain lines.
hermesone installhermesone update is safe to run repeatedly — it no-ops when already current and only downloads when a newer release exists.
hermesone plan [tag] resolves and prints what would be installed — release tag, asset, size, and the expected sha512 — without downloading or installing anything. Use it to show the user before asking them to approve an install.
hermesone <command> [tag]| Command | Description |
|---|---|
install [tag] | Download, verify (sha512), and install Hermes One — latest, or a pinned release tag. |
update [tag] | Update Hermes One if a newer release is available (no-op when current). |
plan [tag] | Show what would be downloaded (tag, asset, size, expected checksum). No changes. |
version | Print the installed Hermes One version, or a "not installed" message. |
help | Show usage. |
| Flag / Env | Effect |
|---|---|
-y, --yes | Skip the confirmation prompt (for non-interactive/scripted installs). |
HERMESONE_VERSION=<tag> | Pin the release tag (same as the [tag] argument). |
HERMESONE_ALLOW_UNVERIFIED=1 | Proceed even if no published checksum is found. Not recommended. |
In an interactive terminal, install renders a confirmation box, a live download progress bar, and per-step status (resolve → download → verify → install). In a non-interactive context it prints plain status lines and never blocks. Color honors NO_COLOR.
| OS | Artifact | Behavior |
|---|---|---|
| macOS | *-mac.zip (signed) | Verified, unzipped, installed into /Applications (or ~/Applications), then launched — no drag. Updates replace in place. |
| Windows | *-setup.exe | Verified, then the installer is launched. |
| Linux | *.AppImage | Verified, marked executable, then launched. |
install/update use the latest release by default. To install a known build, pass a tag or set the env var:
hermesone install v0.6.35
HERMESONE_VERSION=v0.6.35 hermesone installEach download is verified against the base64 sha512 published in the release's electron-builder manifest (latest-mac.yml / latest.yml / latest-linux.yml). On mismatch the file is deleted and nothing is installed. If a release publishes no checksum for the asset, install refuses unless HERMESONE_ALLOW_UNVERIFIED=1 is set. You do not need to verify manually — surface the result from plan to the user and let the package enforce it.
import { plan, install, update, getInstalledVersion } from "hermesone";
// Preview without downloading — show this to the user for approval.
const p = await plan(); // { tag, asset, url, size, sha512 }
// Install (verifies sha512 before installing). Optionally pin a tag, and/or
// subscribe to progress events to render your own UI.
await install({
tag: "v0.6.35",
onProgress: (e) => console.log(e.phase), // resolve|download|verify|extract|launch|installed...
});
await update(); // no-op if already current
const current = await getInstalledVersion(); // e.g. "0.6.35", or nullAlso exported: fetchRelease, parseChecksums, selectAsset, getTarget, isNewer, and types Release, ReleaseAsset, State, Target, InstallOptions, InstallPlan, ProgressEvent. The library prints nothing on its own — all output is driven by your onProgress handler.
CFBundleShortVersionString from Hermes One.app/Contents/Info.plist (/Applications and ~/Applications), so manual installs are recognized too.~/.hermesone/state.json, written after each install/update done through this tool.version returns null (CLI prints "Hermes One is not installed.") when neither source yields a version.npm install hermesone does not download or launch the app — running an installer as a silent side effect of npm install is surprising, so it's opt-in. After installing the package it prints the next step (npx hermesone install). Controls:
Env (set before npm install) | Effect |
|---|---|
| (none) | Prints guidance; does not install the app. |
HERMESONE_AUTO_INSTALL=1 | Runs the install automatically during postinstall. |
HERMESONE_SKIP_INSTALL=1 | Silences the postinstall notice entirely. |
| Symptom | Cause / fix |
|---|---|
No published checksum found for <asset> | The release has no sha512 manifest entry for this asset. Prefer a release that does; only override with HERMESONE_ALLOW_UNVERIFIED=1 if the user accepts it. |
Checksum mismatch for <asset> | The download didn't match the published sha512 — the file was deleted and nothing installed. Retry; if it persists, the release/asset may be compromised or corrupted. |
Failed to fetch release ...: 403 | GitHub API rate limit (unauthenticated). Wait and retry. |
No Hermes One build available for <platform>/<arch> | The release has no asset for this OS/arch. Check the releases page. |
| Prompt didn't appear / it just proceeded | Not a TTY (CI, pipe, agent). That's expected — it runs non-interactively. Use plan first to gate, or --yes to be explicit. |
version says not installed after a manual install | Only macOS auto-detects from disk. On Windows/Linux, install once via this tool so ~/.hermesone/state.json is written. |
fathah/hermes-desktop and run it. The package verifies sha512 and (interactively) prompts, but only run it on explicit user intent — never automatically from an agent workflow.plan to show the release/asset/size/sha512; in non-interactive contexts that preview is your approval gate.© BankrBot, ISC. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in hermesone of BankrBot/skills.
Open the folder on GitHubat commit dc47eed
Hermesone 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 |
|---|---|---|---|---|---|---|
| Hermesone this skillBankrBot/skills | 1.2k | — | ~3.1k | Automated safety check: Pass | ISC | |
| Proxychains Network Fallback2025Emma/vibe-coding-cn | 23k | 1 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Update .NET Supported OS Matrixdotnet/core | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.6k | — | ~3.8k | Automated safety check: Pass | MIT |
2025Emma/vibe-coding-cn
Retries failed network commands through proxychains4 and a local proxy when it sees timeouts, DNS failures or blocked access.
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
BankrBot/skills
Builds onchain apps with Coinbase's OnchainKit React components and TypeScript utilities: wallet connection, identity, token swaps, transactions and checkout flows.
BankrBot/skills
Lists AgenticBets prediction markets on Base, shows odds, places UP or DOWN bets on token prices in USDC and claims winnings through the Bankr wallet API.
BankrBot/skills
Creates AI2Human tasks for steps that need a real person, such as manual QA or local checks, and returns a task URL the agent can track.
BankrBot/skills
Lets an agent inspect and operate AZZLE V2 tasks on Base through Bankr, from posting and claiming to funding, delivery, release and disputes, behind verified deployment pins.
BankrBot/skills
Inspect B20 token contract addresses on Base through B20 Console.
BankrBot/skills
Paste a URL or free text and get matched Polymarket / Hyperliquid / Deribit markets with Quotient edge scores.
Install, update, and manage the Hermes One desktop app via the hermesone npm package. Hermesone is an agent skill from BankrBot/skills. Install, update, and manage the Hermes One desktop app via the hermesone npm package.
Hermesone fits situations like: A user wants to set up Hermes One; upgrade it from the command line; check the installed version; preview a release before installing.
Run `npx skills add BankrBot/skills --skill hermesone -a claude-code`. Or copy the skill folder (hermesone in BankrBot/skills) into .claude/skills/hermesone in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BankrBot/skills --skill hermesone -a codex`. Or copy the skill folder (hermesone in BankrBot/skills) into .agents/skills/hermesone in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BankrBot/skills --skill hermesone -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hermesone, .gemini/skills/hermesone, .github/skills/hermesone and .opencode/skills/hermesone in your project.
Going by SKILL.md and its folder, Hermesone needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64/x64), Windows (setup.exe), Linux (.AppImage). The interactive UI needs a TTY; in non-interactive contexts it falls back to plain output. Works in Claude Code and any environment with a shell and npm..
SKILL.md names 3 domains. As links in the text: github.com, hermesone.org and bankr.bot. This is read from the text; nothing was executed.
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.
Hermesone is published under the ISC licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Hermesone: Proxychains Network Fallback (2025Emma/vibe-coding-cn, 23k stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Update .NET Supported OS Matrix (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BankrBot (a GitHub organization) maintains it in BankrBot/skills, which has 1,202 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on October 10, 2026.
Source: BankrBot/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.