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/jdanigo/hydraia/dashboardgit clone --depth 1 https://github.com/jdanigo/hydraiaWrote 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/jdanigo/hydraia/dashboard)<a href="https://agentmods.dev/commands/jdanigo/hydraia/dashboard"><img src="https://agentmods.dev/badge/commands/jdanigo/hydraia/dashboard.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.00374 |
| Opus 5 | $0.00009 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
dashboard 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 3d 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
Start the Hydraia dashboard — a local, zero-dependency web server (Node built-ins
only) bound to 127.0.0.1 (never exposed to the network). It shows plugin status
(version, skills, agents, hooks, MCP servers, dependency health), local usage
telemetry (agents, models, tokens, skills — all recorded locally, never
transmitted), and lets you edit the run modes (agent caps, spec-drive, telemetry,
review rigor, and more).
- Resolve the plugin root and the port (default from config, or
$ARGUMENTSif given):ROOT="${CLAUDE_PLUGIN_ROOT:-$(cat "${HOME}/.cache/hydraia/plugin-root" 2>/dev/null)}" [ -n "$ROOT" ] || ROOT="$(ls -d "${HOME}/.claude/plugins/cache/hydraia/hydraia/"*/ 2>/dev/null | sort -V | tail -1)" - Start it in the background so it keeps running:
node "$ROOT/dashboard/server.js" $ARGUMENTS - It prints
Hydraia dashboard running at http://127.0.0.1:<port>. Show me that URL and open it in my browser (openon macOS,xdg-openon Linux,starton Windows). Tell me to stop it with Ctrl-C (or by ending the background process).
If Node is not installed, say so and point me at /hydraia:doctor. Never bind to
anything other than 127.0.0.1.
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.
- 3d ago First seen · 27 lines · 18 tokens per session scan A f3ec76ca54f8
dashboard is a command published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 374 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 commands, from other repositories
test
Run the app's microflow tests and verify it in the browser.
live-verify
Two-part gate for gflow-cli feature work — pre-flight state check at the start, live-verification against real Flow before claiming done.
execute-scenario
Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
check-access
Check whether a user or group can access a specific URL via ZIA policies.
browser
Debug and fix browser issues by inspecting, diagnosing, and resolving visual or technical problems.