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-debug-loop/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-debug-loop)<a href="https://agentmods.dev/skills/dohooo/helmor/helmor-debug-loop"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-debug-loop/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-debug-loop"><img src="https://agentmods.dev/badge/skills/dohooo/helmor/helmor-debug-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Privilege Escalation · line 25 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00100 | $0.00751 |
| Opus 5.5 | $0.00040 | $0.00300 |
| Sonnet 5.5 | $0.00020 | $0.00150 |
| Haiku 4.5 | $0.00010 | $0.00075 |
Grade A, and why
helmor-debug-loop 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helmor Debug Loop
Use this skill to drive a bounded reproduce -> instrument -> inspect -> fix -> verify loop for Helmor local-dev bugs. Always use $helmor-debug-operate for actual local app control through Tauri MCP; this skill owns the debugging strategy and evidence discipline.
Core Loop
- Define the suspected behavior, expected behavior, and success signal in one or two sentences.
- Reproduce through
$helmor-debug-operatewith real UI actions when possible. Start with screenshots, DOM/accessibility snapshots, IPC monitor, console/system logs, and terminal buffers. - If evidence is insufficient, add the smallest temporary log or probe with a unique prefix such as
[debug-loop:<slug>], rerun the flow, then remove or justify the probe before finalizing. - Analyze the evidence before editing product code. Prefer a narrow fix that explains the observed signal.
- Verify the fix with the same user path. For user-visible flows, require three consecutive successful runs unless the user explicitly lowers the bar.
- Produce an evidence pack under
.agent-contexts/<task-slug>/with repro attempts, logs, screenshots, IPC, fix summary, and remaining uncertainty.
Fault Tolerance
- If you cannot reproduce after three distinct attempts, do not invent a failure. Mark the state as
not reproduced, preserve evidence, inspect code paths that should have fired, and report the most likely missing precondition. - If the bug is flaky, run at least three attempts and compare evidence. Treat intermittent pass/fail as a valid finding, not a failure of the loop.
- If Tauri MCP cannot connect, use
$helmor-debug-operaterecovery steps. If the bridge remains unavailable, fall back to static code analysis and terminal tests, and label UI verification as blocked. - If a skill recipe fails three times, follow
$helmor-debug-operatestale-skill rules: reason from fresh screenshots/DOM/code, record a candidate skill update, and ask before editing that skill unless the user explicitly requested it. - If adding logs risks exposing secrets, log shape/count/state only. Never print access tokens, credentials, API keys, cookies, or private account details.
- If verification cannot be run safely because it would mutate durable user data, switch to a disposable workspace/session or stop and state the risk.
What ships with it
4 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 · 39 lines · 100 tokens per session scan A 4ce3dd038c93
helmor-debug-loop is a skill published in the GitHub repository dohooo/helmor (1,309 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 751 once invoked, about $0.0004 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
add-plugin
Use when installing, disabling, enabling, or troubleshooting a third-party octomux plugin — the manifest row shape, octomux plugins list/disable/enable, reading octomux doctor output, and recovering a broken boot with --safe-mode.
create-task
Use when creating an octomux task to dispatch autonomous Claude Code agents for building features, fixing bugs, or any code changes.
video-quality
Validate a candidate video technically, visually, and editorially before presenting it as complete. Use after rendering a video or when diagnosing playback, aspect ratio, duration, audio, captions, black frames, freezes, identity drift, or other quality problems.
hyperframes-quality
Review and gate an editable HyperFrames composition or its rendered video before delivery. Use after building, revising, diagnosing, or rendering a HyperFrames project when layout, contrast, deterministic timing, transitions, animation choreography, rendered-frame fidelity, or high-quality acceptance needs…
browser-test-self-healing
Build an AgentWorks workflow that diagnoses a browser-test failure, proposes a test-only repair, verifies it in isolation, obtains the configured review, and updates canonical tests and application knowledge. Use for stale or flaky browser automation, not product defects.
flaky-test-detection-stabilization
Build AgentWorks browser-test flake detection and reviewed stabilization using repeated isolated attempts and evidence comparison. Use when identical test inputs produce inconsistent outcomes.