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/observabilitygit clone --depth 1 https://github.com/jdanigo/hydraiaWhat 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.00023 | $0.00265 |
| Opus 5 | $0.00012 | $0.00133 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
observability 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
Dispatch the sre-observability agent. Add structured logging (correlation IDs), RED/USE metrics, OpenTelemetry traces, health/readiness endpoints, and alert rules as plan tasks. Redaction is absolute — never log secrets, tokens, or PII; review every proposed signal for leakage. Vendor-agnostic: OTel first, vendor SDKs only if already in the repo (never add a new APM dependency). Wiring alerts/dashboards to a live backend is a flagged human step. Report what was instrumented and the redaction decisions.
Request: $ARGUMENTS
When finished, record telemetry for this run: printf 'brief\n' > <base>/.run-complete (where <base> is the artifacts dir resolved at the storage gate — docs/hydraia/ by default, or the external dir if chosen). The Stop hook logs this run's real token/model/sub-agent usage to the local dashboard (delta-scoped per session, so it never double-counts). Do not hand-write the numbers.
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 · 11 lines · 23 tokens per session scan A a03af2bea760
observability is a command published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 265 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
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
proposal
Create a structured feature proposal in docs/11-proposals/.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
issue-resolve
Drive an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG, with localized verifiable scope) to a fix: isolated worktree off develop, test-first fix, /gflow:check, then a DRAFT PR for human review. Mutating and gated — runs inside a strict action envelope (never merges, never spends credits, never marks a…