Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add zeikar/hyperclaude/plugin install hyperclaudeWrote 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/zeikar/hyperclaude/hyper-auto)<a href="https://agentmods.dev/skills/zeikar/hyperclaude/hyper-auto"><img src="https://agentmods.dev/badge/skills/zeikar/hyperclaude/hyper-auto/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/zeikar/hyperclaude/hyper-auto"><img src="https://agentmods.dev/badge/skills/zeikar/hyperclaude/hyper-auto.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00080 | $0.01767 |
| Opus 5.5 | $0.00032 | $0.00707 |
| Sonnet 5.5 | $0.00016 | $0.00353 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
hyper-auto 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 8d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hyper-auto — chain hyper-plan-loop into hyper-implement-loop
Single-gesture pipeline: hyper-plan-loop converges → hyper-implement-loop runs on the produced plan. Stops cleanly at any terminal state in between. No cron, no merge, no push, no autonomous follow-up rounds — just the two loops, chained.
When to use
- User has a task description and wants the full plan-harden → implement-harden chain in one go.
When to skip
- A plan already exists → use
/hyperclaude:hyper-implement-loopdirectly. - User wants to inspect / hand-edit the plan before implementing → use
/hyperclaude:hyper-plan-loop, then decide.
Procedure
Step 1 — Run hyper-plan-loop
Invoke /hyperclaude:hyper-plan-loop <task> with the user's task description verbatim, minus any seat override. Let it run to terminal state.
Each inner loop seats its own reviewer per ${CLAUDE_PLUGIN_ROOT}/references/reviewer-seat.md; a "review with Claude" / "use Codex" given to hyper-auto decides both loops' seats.
Step 2 — Branch on plan-loop's terminal state
- Clean exit (no blocking findings — plan-loop converged) → capture the plan path from the loop's report, proceed to Step 3.
- Cap reached (plan-loop's "revise loop" report — blocking findings still open after the seat's review budget) → STOP. Surface plan-loop's terminal report verbatim. Do NOT proceed.
- Any other terminal failure (bridge failure, planner-write/format failure, reply-contract failure, unparseable review, etc.) → STOP, surface the underlying report verbatim.
Implementing on a plan with unresolved blocking findings wastes the implement-loop budget on a known-broken input — this is the safety boundary.
Step 3 — Run hyper-implement-loop
Invoke /hyperclaude:hyper-implement-loop <plan-path-from-Step-1> with the canonical plan path captured from plan-loop's report. Let it run to terminal state.
Step 4 — Auto-recap, then compose the report
On a clean composed exit (guard below), FIRST run the terminal recap, THEN emit the composed report so the report can quote the actual written recap path. On any non-clean terminal the recap is skipped entirely.
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.
- 8d ago Changed 9b520e35f4ff
- 24d ago Changed ee75e091b9fb
- 25d ago Changed · +4 lines 84d714a5d975
- 1mo ago First seen · 84 lines · 80 tokens per session scan A 56a9da568d18
hyper-auto is a skill published in the GitHub repository zeikar/hyperclaude (4 stars, last pushed 10d ago), licensed MIT. It adds 80 tokens to every session and 1,767 once invoked, about $0.0003 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-31.
Other skills, from other repositories
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
ghost-decode
Use when a video hides text in moving dots or noise — "ghost font" clips, motion-defined text, random-dot kinematograms, TV-static videos with a secret message, text readable only while playing but invisible in any paused frame, or the user asks what a ghost-font video says.
embedded-systems-architect
Embedded systems and Edge AI architecture assistant for development-board projects. Use when the user works with dev boards, SoC, MCU or microcontroller (datasheet, TRM, HDK, schematics), firmware or RTOS development, cross-compilation, SDK / BSP / sample code, board families such as Jetson, Raspberry Pi, ESP32…
boss
Act as the boss — delegate the task to a free opencode agent, review its output, request revisions, and only after the user approves, supervise deployment end-to-end. Claude does not write code or do heavy implementation in this mode. Use when the user says "be the boss", "/claudeboss:boss", or wants Claude to manage…
obsidian-companion
Use when interacting with the user's Obsidian vault — reading, writing, searching, or chatting with notes using local RAG. Guides tool selection and writing strategy for all vault operations.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…