helmor-cli

A command-line tool for controlling Helmor, a development environment for repositories, workspaces, sessions, files, and AI agents. It also provides workflows for organizing related changes into dependent pull requests.

In plain words
What is it for?
Use it to inspect Helmor settings and data, manage workspaces and sessions, send prompts to agents, work with GitHub, run Helmor as an MCP server, or create and reorganize stacked pull requests.
Why use it?
It lets you inspect and manage Helmor from a terminal instead of navigating its interface manually. It also helps handle large changes that need to be split across several dependent pull requests.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dohooo/helmor/helmor-cli
Any agent
npx skills add dohooo/helmor --skill helmor-cli
Clone the repo
git clone --depth 1 https://github.com/dohooo/helmor

Made for: Claude Code, Codex.

Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00158 $0.01183
Opus 5 $0.00079 $0.00592
Sonnet 5 $0.00032 $0.00237
Haiku 4.5 $0.00016 $0.00118

Measured 2d ago against content hash 40b8c490c74a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

helmor-cli 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/render_stack.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/helmor-cli/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Helmor CLI

Use this skill to guide simple terminal-first Helmor workflows. Keep the answer practical: prefer one or two concrete commands over a long CLI tutorial.

Command Routing

Route by the first word after /helmor-cli:

  • restack — re-sync a PR stack after a lower layer changed or merged. Follow references/restack.md. (This is what the composer's Restack button sends.)
  • stack — plan and build a large change as a stack of dependent PRs. Follow references/stacked-pr.md.
  • break — split the change you've ALREADY written in the current workspace into a stack of smaller dependent PRs, confirming the slicing granularity with the user first. Follow references/break.md.
  • Anything else (or no argument) — an ordinary Helmor CLI task; use the binary-name guidance and command reference below.

Binary Name (Release vs Dev)

Examples below use the literal name helmor — the binary a release user has on their PATH.

  • Release builds: invoke commands as helmor <subcommand>.
  • Dev builds: do NOT assume helmor-dev is on PATH. Under Helmor's worktree-based dev workflow every worktree has its own target/debug/helmor-cli, and a shared /usr/local/bin/helmor-dev symlink (if it exists) can only point at one of them. Instead:
    • If you're an agent running inside Helmor, the system prompt has already handed you the exact CLI invocation to use (typically an absolute path like <worktree>/src-tauri/target/debug/helmor-cli). Call it verbatim — don't re-verify with which / file / --version.
    • If you're a human at a terminal, run <your-worktree>/src-tauri/target/debug/helmor-cli <subcommand> (or whatever path your active Helmor build uses).

The rest of every command shape is identical regardless of build.

First Checks

  1. Check whether the CLI is installed and which data mode it targets:
helmor cli-status
  1. Check the active data directory and database:
helmor data

Use --json when the output will be parsed by scripts or another tool.

Read the full file on GitHub · 133 lines

Files

What ships with it

7 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.

Changes

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.

  1. 2d ago First seen · 133 lines · 158 tokens per session scan A 40b8c490c74a

Subscribe to this mod's changes

helmor-cli is a skill published in the GitHub repository dohooo/helmor (1,297 stars, last pushed 11d ago), licensed Apache-2.0. It adds 158 tokens to every session and 1,183 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

execution

M-1.4 execution skill — 跑 single task 产 patch + 提交 envelope。.

Towow-ai/Flowness · 22 tokens

review

M-1.5 review skill — 在 patch 跟 contract 之间找 finding,produce Finding 一等对象。.

Towow-ai/Flowness · 26 tokens

fix-self-check

M-1.6 envelope self-check——独立性保证不自欺欺人 (5 blockingcheck)。由 CLI ./tw fix complete --self-check-mode fork(默认即 fork)自动派起,不经 Skill 工具调用;fix 主会话产 FixCompleted 前直读本文,是为理解双层验证关系。.

Towow-ai/Flowness · 74 tokens

plan-decompose

从 completioncondition + conceptgraph 递归分解出 primitive task 提案。主 planner session 决定接受/调整/拆得更细。.

Towow-ai/Flowness · 36 tokens

dependency-analyze

从 task 的 read/write set + concept statemachine 推导 6 种依赖类型的提案。主 planner 决定边的真实性。派它时只给 read/write set 与疑点、不给预期边集;已有预判逐条标「待复核」交它取证。.

Towow-ai/Flowness · 70 tokens

downtime-recovery

停机后复工的标准安全流程(水位线追平/积压泄流/服务分批重启)。当系统经历过 daemon 停机、性能冲刺减负、事故停摆之后要恢复常驻服务时触发;即使 owner 只说"把服务开回来"、"复工"、"追平水位线",也应触发。核心使命:绝不让"重启"变成"积压喷发"(2026-07-04 实锤:orchestrator 停机后水位线落后 3240 条,直接重启把机器负载打到 22+,owner 被迫立即紧急关停)。.

Towow-ai/Flowness · 157 tokens