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-cli/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-cli)<a href="https://agentmods.dev/skills/dohooo/helmor/helmor-cli"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-cli/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-cli"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00158 | $0.01183 |
| Opus 5.5 | $0.00063 | $0.00473 |
| Sonnet 5.5 | $0.00032 | $0.00237 |
| Haiku 4.5 | $0.00016 | $0.00118 |
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 1mo 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 — 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. Followreferences/restack.md. (This is what the composer's Restack button sends.)stack— plan and build a large change as a stack of dependent PRs. Followreferences/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. Followreferences/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-devis on PATH. Under Helmor's worktree-based dev workflow every worktree has its owntarget/debug/helmor-cli, and a shared/usr/local/bin/helmor-devsymlink (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 withwhich/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).
- 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
The rest of every command shape is identical regardless of build.
First Checks
- Check whether the CLI is installed and which data mode it targets:
helmor cli-status
- Check the active data directory and database:
helmor data
Use --json when the output will be parsed by scripts or another tool.
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.
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.
- 1mo ago First seen · 133 lines · 158 tokens per session scan A 40b8c490c74a
helmor-cli is a skill published in the GitHub repository dohooo/helmor (1,309 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 158 tokens to every session and 1,183 once invoked, about $0.0006 per session on Opus 5.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
skill
Skill "skill" from wavyrai/tmux-ide, covering tmux-ide — claude code skill, when to use, the agent contract, coordinating with other agents and fleet control from the cli.
review-deep
Drive the deep-review phase of an automated PR review. Consumes the walkthrough, runs the deterministic deep-review workflow (parallel lenses → adversarial validation → code-enforced threshold/caps), drafts the surviving findings, and completes the review run.
implement
Implement a Jira ticket — fetches ticket, checks for existing plan, creates worktree branch, runs implementation with verification. Usage - /implement IN-XXX.
plan-week
Weekly planning session — AI interviews you about goals, breaks them into Jira tickets with lightweight plans, creates them after approval. Use when starting the week or planning a batch of work.
plan
Deep planning for a specific Jira ticket — codebase deep-dive, interview on ambiguous points, update ticket with detailed approach. Use before implementing large or unclear tickets. Usage - /plan IN-XXX.
update-task-status
Use when you want to update the workflow status of an octomux task, add a note, rename it, or link external references (e.g. Jira tickets).