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/export-tracesgit clone --depth 1 https://github.com/TheArcForge/HadesWhat 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.00015 | $0.00251 |
| Opus 5 | $0.00008 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
hades-export-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 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.
What it actually says
Help the user export trace data. The database location depends on what they have installed for this project:
- Standalone app (v2, the default today): the SQLite file is in Hades' app storage, not the project folder:
~/Library/Application Support/Hades/projects/<productGUID>/traces.db. Theprojecthandlehades_statusreturns for this project is that productGUID. - Legacy Unity package (v1.2), if still installed in this project: the SQLite file is at
<project>/.arcforge/traces.db, inside the project itself.
Either way:
- The database file can be opened with any SQLite client (DB Browser for SQLite, DBeaver, sqlite3 CLI).
- For sharing: the user can copy the trace database file. It contains all trace and span data.
Tables of interest:
traces— top-level trace records (one per MCP tool call)spans— individual spans within traces (nested operations)
Privacy note: traces may contain file paths and query parameters from the project. Review before sharing externally.
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 · 20 lines · 15 tokens per session scan A d661cd6d6019
hades-export-traces is a command published in the GitHub repository TheArcForge/Hades (27 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 251 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
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
statusbar-theme
Switch the status-bar color theme (graphite / twilight / linen).
statusbar-preview
Render every style × theme combination using your real cached data.
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.
check-tcc
Print che-ical-mcp's current TCC permission state, binary path, and ready-to-paste reset / re-prompt commands. Use when user says "check TCC", "permission status", "tccutil"。.