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 commands/thearcforge/hades/show-tracesgit clone --depth 1 https://github.com/TheArcForge/HadesWrote 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/commands/thearcforge/hades/show-traces)<a href="https://agentmods.dev/commands/thearcforge/hades/show-traces"><img src="https://agentmods.dev/badge/commands/thearcforge/hades/show-traces.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00273 |
| Opus 5 | $0.00009 | $0.00137 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
hades-show-traces 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 4d 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
Direct the user to the trace explorer. Two possible UIs, depending on what they have installed for this project:
- Standalone app (v2, the default today): open the Hades app (menu bar icon → Open Hades) and select Traces in the sidebar. Filter by project, tool, outcome, and duration; drill into a call's span detail.
- Legacy Unity package (v1.2), if still installed in this project: Hades > Open Charon Dashboard from Unity's menu bar opens a browser-based trace dashboard reading this project's
.arcforge/traces.dbdirectly.
If unsure which the user has, ask, or default to describing (1) — every v2 Claude Code plugin install has the standalone app; the Unity menu item only exists if the legacy package is also still installed, which Claude cannot check from this session.
Neither path is reachable through an MCP tool call — hades_charon_status reports Unity Editor attachment (is a live Editor connected, is it busy), not trace or dashboard state. There is no MCP tool that returns trace records; one of the two UIs above is the only way to see them.
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.
- 4d ago First seen · 14 lines · 18 tokens per session scan A e2079c27ba47
hades-show-traces is a command published in the GitHub repository TheArcForge/Hades (27 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 273 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-30.
Other commands, from other repositories
create-skill
Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).
sync-config
Sync a scraping config's URLs against the live documentation site.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.
docs-update
You are executing the /dogma:docs-update command. Your task is to synchronize documentation across README files and wiki articles, ensuring everything is up-to-date.