Helmor is a local workbench for running and coordinating multiple coding agents, with each task isolated in its own Git workspace. Developers use it to review changes, test code, resolve conflicts, and merge or create pull requests. Its catalogue entries extend Helmor with skills, instructions, settings, and hooks.
Borrowing it
Nothing to install: this file belongs to dohooo/helmor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dohooo/helmor/main/.agents/skills/helmor-bump-vendors/SKILL.mdgit clone --depth 1 https://github.com/dohooo/helmorWrote 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/dohooo/helmor/helmor-bump-vendors)<a href="https://agentmods.dev/skills/dohooo/helmor/helmor-bump-vendors"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-bump-vendors/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/dohooo/helmor/helmor-bump-vendors"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-bump-vendors.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 Data Exfiltration · line 44 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00185 | $0.02147 |
| Opus 5 | $0.00093 | $0.01073 |
| Sonnet 5 | $0.00037 | $0.00429 |
| Haiku 4.5 | $0.00018 | $0.00215 |
Grade A, and why
helmor-bump-vendors 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helmor Bump Vendors
Standardized procedure for upgrading the third-party agent CLIs, SDKs, and helper binaries that Helmor pins and bundles. Goal: a correct, verified bump with no guesswork about where versions live, how to source each SHA256, or what to run before declaring it done.
The pin sites
Every bundled version is pinned in one (or both) of these files:
sidecar/package.json— npm dependencies. Covers SDKs (imported in TS) and the npm-distributed CLIs whose native binary is staged fromnode_modules(@anthropic-ai/claude-code,@openai/codex,opencode-ai).sidecar/scripts/vendor-platform.ts— version constants + per-version SHA256 tables for every staged binary. Source of truth for what gets bundled into the release.sidecar/scripts/stage-vendor.ts— staging logic. Only edit it when a vendor's archive layout changes (rare; see codex/cursor notes inreferences/vendors.md).
Vendor classes (determine the change-set)
| Class | Vendors | What to edit | SHA256? |
|---|---|---|---|
| A. npm SDK only | @anthropic-ai/claude-agent-sdk, @cursor/sdk, @opencode-ai/sdk, @earendil-works/pi-* |
package.json line |
No — plain npm dep |
| B. npm-distributed staged binary | claude-code, codex, opencode | package.json line + SHA256 table key in vendor-platform.ts |
Yes — from npm tarball |
| C. GitHub-release staged binary | kimi, gh, glab, cloudflared, llama.cpp, node | <NAME>_VERSION const + SHA256 table in vendor-platform.ts (NOT in package.json) |
Yes — source varies |
Per-vendor exact pin location, SHA256 source, and gotchas live in references/vendors.md —
read the relevant section before editing.
Workflow
- Scope. Confirm which vendors to bump. For each, open
references/vendors.mdfor its class, pin location, SHA source, and gotchas. - Find the target version. Check LIVE — never trust memory; dist-tags flip within hours.
- npm:
bun -e 'console.log((await (await fetch("https://registry.npmjs.org/<pkg>")).json())["dist-tags"])'Targetlatest(the stable channel).nextis a prerelease — do not pin it unless the user explicitly asks. claude-code also publishes a conservativestabletag that lags (e.g.2.1.179); Helmor trackslatest, notstable. - GitHub-release vendors: check the repo's Releases (or
https://api.github.com/repos/<owner>/<repo>/releases).
- npm:
- Edit the pins (
package.jsonand/or the_VERSIONconst). Apply the Claude lockstep rule and any per-vendor gotcha from the reference. cd sidecar && bun install— pulls the new versions. Sanity-check: resolved versions are correct, any removed deps dropped frombun.lock, transitive deps you rely on are still present.- Compute + fill SHA256 for class B/C. Use
scripts/npm_vendor_sha.shfor B; see the reference for C. Botharm64andx64are mandatory (see Critical rules). - Run the verification gates (below) — all must pass.
- Create release metadata. Once the gates pass, invoke the
/helmor-releaseskill to draft the changeset (and an in-app announcement if the bump warrants one). Don't skip this — a vendor bump is a user-visible change and needs a changeset. A routine bundled-agent refresh is typically apatchchangeset with no announcement; the body should name the user-visible change (which agents moved to latest), not the internal cleanup (Pi removal, pin tidy-ups, doc fixes). - Report: current → target per vendor, breaking-change assessment, gate results, exact files touched, and the changeset created. Leave commit / PR to the user unless asked.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 113 lines · 185 tokens per session scan A 9bb7c6746983
helmor-bump-vendors is a skill published in the GitHub repository dohooo/helmor (1,304 stars, last pushed 19d ago), licensed Apache-2.0. It adds 185 tokens to every session and 2,147 once invoked, about $0.0009 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
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
checking-release-readiness
Records a ship, block, defer, or ship-with-risk decision that ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together. Use when a packet, PR, release, dependency change, or agent-authority change approaches merge. Do not use early in development before evidence exists.
publish
Bump version, build, test, publish to npm, and install locally.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
release
Release Aigon — push to origin, cut a version+tag, or publish to npm. Wraps scripts/ship.js with CHANGELOG draft + dry-run preview. Triggers when the user types "/release", "/push", "/ship", or says "ship a release", "publish a beta", "cut a version", "push to origin", "release X to npm".