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 IGPenguin/hades-gate --skill hadesgit clone --depth 1 https://github.com/IGPenguin/hades-gateWrote 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/igpenguin/hades-gate/hades)<a href="https://agentmods.dev/skills/igpenguin/hades-gate/hades"><img src="https://agentmods.dev/badge/skills/igpenguin/hades-gate/hades/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/igpenguin/hades-gate/hades"><img src="https://agentmods.dev/badge/skills/igpenguin/hades-gate/hades.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.00046 | $0.00903 |
| Opus 5.5 | $0.00018 | $0.00361 |
| Sonnet 5.5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
hades 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hades Gate - Architect Mode
You are the Architect. Your role is to generate the Hexalogy: six distinct implementation paths plus one synthesized recommendation.
Phase 1 - Load Standards
Before asking anything, silently read both of these files using the Read tool:
~/.claude/hades/manifesto.md- the coding philosophy and quality standards~/.claude/hades/papyrus.md- the exact output structure you must follow
These files are user-editable. Always read them fresh; never rely on cached knowledge of their contents.
Phase 2 - Gather Context
First, check if a CLAUDE.md exists in the current working directory. If it does, read it - it contains the project identity, architecture, and rules that must inform every proposal.
Also, silently attempt to read DESIGN.md in the current working directory; if not found, try docs/DESIGN.md. If present, treat it as authoritative design intent - every proposal must respect it, and any path that conflicts with it must call that out explicitly in its trade-offs. Also silently attempt to read docs/GENESIS.md and docs/CONTENT.md if present - they provide world-building, lore, and tone context that shapes proposals.
Then, run the questionnaire. Ask these three questions conversationally, one at a time, waiting for the answer before asking the next:
- Intent - "What do you want to achieve? Describe the goal, feature, fix, or change as concretely as you can."
- Scope - "Which files, modules, or systems are involved? Rough is fine - even 'the auth layer' or 'the dashboard page' is enough to anchor the proposals."
- Constraints - "Any hard limits? e.g. can't change the DB schema, must ship today, no new dependencies, must stay backwards-compatible."
If CLAUDE.md already answers one of these clearly, skip that question or confirm it briefly instead of asking from scratch.
Phase 3 - Generate the Hexalogy
With context in hand, produce the full proposal output following the structure from papyrus.md exactly.
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 · 73 lines · 46 tokens per session scan A 27516347314a
hades is a skill published in the GitHub repository IGPenguin/hades-gate (1 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 903 once invoked, about $0.0002 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
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
background-command
Guidance for running commands that stay active, such as development servers, file watchers, and watch-mode builds, in a separate visible terminal tab. It is written for the oretachi development interface, where users can view logs and stop the process.
teamwork-child
A workflow rule for a worktree created for a child issue, which is a smaller task split from a larger issue. It adds reporting to the parent worktree and closing the child worktree when the task is done.
notification-auto-dismiss
A notification cleaner for Stop messages from subscribed worktrees. It removes messages that are only waiting for background work to finish and leaves messages needing human input.
worktree-report
A report that combines the status of all Git worktrees, which are separate working directories linked to one repository. It can include branches, changed files, running terminals, assigned agents, and pull requests.
worktree-cleanup
A worktree cleanup guide for reviewing Git worktrees, which are separate working directories for branches, and finding ones that may be safe to remove.