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-setupnpx skills add zeikar/hyperclaude --skill hyper-setupgit 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.00013 | $0.01025 |
| Opus 5 | $0.00006 | $0.00513 |
| Sonnet 5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
hyper-setup 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hyper-setup
Run the doctor probe. Parse the JSON it emits and report per-check status plus the overall verdict.
Prerequisite probe: !node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-doctor.mjs"
What it checks
The probe emits one JSON line: { ok, checks: [{name, detected, required, status, severity, remediation}] }.
The five checks:
- Node.js >= 18 — severity: hard. hyperclaude's bridge is stdlib Node; versions below 18 are unsupported.
- codex-cli >= 0.130.0 on PATH — severity: hard. Version-floor check only (no capability probe). The bridge spawns
codex exec; the tool must be present and at a known-good version. - git on PATH — severity: hard. The bridge reads git state for slug generation and diff targets.
codex --searchglobal flag (pre-subcommand) — severity: hard. The bridge passes--searchas a global flag before the subcommand on every Codex spawn; codex-cli must acceptcodex --search exec --help(exit 0).- Claude Code >= 2.1.232 — severity: conditional. 2.1.232 is the known-good floor for the background-agent transport
hyper-plan-loop,hyper-implement-loop,hyper-docs-loop, andhyper-auto(which chains hyper-plan-loop → hyper-implement-loop) use to reach their agent. Surfaced, not gated: a below-floor or unknown version (claudeoff PATH, unparseable output) is a WARN that never flips the verdict and blocks nothing — the full research→plan→implement flow works regardless.
Reporting directive
The inline probe above runs automatically; parse the single JSON line it emitted to stdout (do not run it again).
Distinguish by shape before deciding how to report:
- If the JSON has a
checks[]array — render the per-check table and verdict. This includes the normalok:false"prerequisites failing" case. Do NOT use the fallback for this shape. - ONLY if there is no parseable JSON at all, or the JSON has an
errorkey (the{ok:false,error:...}probe-failure shape with no usablechecks[]) — use the fallback sentence below; never the fallback for a normalok:falseresult that haschecks[].
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.
- yesterday First seen · 57 lines · 13 tokens per session scan A d90b4a965c64
hyper-setup is a skill published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 1,025 once invoked, about $0.0001 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
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.
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
golden-rss
Use when testing the rss golden build.
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.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
golden-chat-topics
Use when testing the goldenchattopics golden build.