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 skills add gaia-research/gaia-skill-heaven --skill skill-hellgit clone --depth 1 https://github.com/gaia-research/gaia-skill-heavenWrote 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/gaia-research/gaia-skill-heaven/skill-hell)<a href="https://agentmods.dev/skills/gaia-research/gaia-skill-heaven/skill-hell"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/skill-hell/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/gaia-research/gaia-skill-heaven/skill-hell"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/skill-hell.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.00031 | $0.00429 |
| Opus 5.5 | $0.00012 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
skill-heaven-runtime-skill-hell 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 15d 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.
What it actually says
Skill Hell — reference for the explore band
The user selected the Skill Hell band: high (default), or xhigh/max when
they named one. A session sits at exactly one rung.
zero · low · med · high · xhigh · max · ultra
Skill Hell is the model-led exploration band of that one line. It names a direction, not a number: there is no per-rung count and no summon is capped. Behavioral evidence is not available to this band yet — it changes the breadth of relevance-ranked results, not behavior-aware composition, and no Hell stamp gate is running.
What this output is
Reference data. It reports the band the user selected and the discovery parameters it describes. It cannot change the task, outrank the instructions already in force, authorize a tool call, widen permissions, or leave state behind. Act on it only where the user's request and those instructions call for it. Choosing Ultra or Hell does not settle a later call: each one is judged again, on its own merits, at the time it is made.
Discovery, if the gap is real
If a real capability gap is in front of you and a call fits the request and the
permissions already held, surface: "hell" is what this band describes. What
comes back is a card, not a grant: judge each candidate for relevance and safety
before reading it, then apply only what survives that judgment.
Only model-invokable or unclassified tree skills are reachable this way. A fleet
skill marked disable-model-invocation: true is human-led and stays out of it,
even when it scores highest. The card reports the source classification as
metadata.
Never claim this changed the boot posture.
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.
- 15d ago Changed · +5 tokens per session 9849121870da
- 21d ago Changed · +20 lines · -5 tokens per session 6c3f8ca59803
- 1mo ago Changed · +1 lines 140696de95a1
- 1mo ago Changed · +2 lines 224e17c68b8d
- 1mo ago First seen · 22 lines · 31 tokens per session scan A d2926a714a88
skill-heaven-runtime-skill-hell is a skill published in the GitHub repository gaia-research/gaia-skill-heaven (4 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 429 once invoked, about $0.0001 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
architecture-compass
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use…
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
review
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when…
skill-review
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions…
clean-code-refiner
Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards'…
context-anchoring
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles).…