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.
npx agentmods add skills/zeikar/hyperclaude/hyper-autonpx skills add zeikar/hyperclaude --skill hyper-autogit clone --depth 1 https://github.com/zeikar/hyperclaudeWhat 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 | $0.00080 | $0.01641 |
| Opus 5 | $0.00040 | $0.00821 |
| Sonnet 5 | $0.00016 | $0.00328 |
| Haiku 4.5 | $0.00008 | $0.00164 |
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 2d 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 — 84 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. Let it run to terminal state.
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 10-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.
Clean-exit guard. Auto-recap fires ONLY when ALL of these hold:
- plan-loop exited clean (Step 2's clean-exit branch — not cap/failure), AND
- implement-loop reached its Step 7 review-convergence report (not a Step 6 cap/failure STOP), AND
- that Step 7's
fix(review):convergence commit reported SUCCESS (commit SHA + clean tree) OR SKIP (nothing staged, clean tree).
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.
- 2d ago First seen · 84 lines · 80 tokens per session scan A 56a9da568d18
hyper-auto is a skill published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 80 tokens to every session and 1,641 once invoked, about $0.0004 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-31.
Other skills, from other repositories
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
golden-rss
Use when testing the rss golden build.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.