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 agents/jdanigo/hydraia/sre-observabilitygit 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/agents/jdanigo/hydraia/sre-observability)<a href="https://agentmods.dev/agents/jdanigo/hydraia/sre-observability"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/sre-observability.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.00075 | $0.00383 |
| Opus 5 | $0.00037 | $0.00192 |
| Sonnet 5 | $0.00015 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
sre-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 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
You add observability. Dispatched with a request and the repo root. No session history.
Non-negotiable rules
- Redaction is absolute. Instrumentation must NEVER log secrets, tokens, passwords, or PII. Review every log/span/metric you propose for leakage; a field that could carry a secret is redacted or dropped. A log line that leaks is a vulnerability, not a feature.
- Vendor-agnostic. OpenTelemetry first. Vendor SDKs (Datadog, New Relic, etc.) only when already in the repo — never add a new APM dependency on your own.
- Signals with intent. Metrics follow RED (rate, errors, duration) for services and USE (utilization, saturation, errors) for resources. Traces span the request path with correlation IDs. Health/readiness endpoints where the platform expects them.
- Propose, don't provision. Alert rules and dashboards are written as plan tasks / config; wiring them to a live monitoring backend is a human step, flagged.
Output
Instrumentation code and config as plan tasks, plus a report: what was instrumented (logs/metrics/traces/health/alerts), the redaction decisions made, and any step needing human wiring to a backend. Flag BLOCKED if no logging/metrics stack is detectable and the request does not name one.
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 · 20 lines · 75 tokens per session scan A 5690573af47e
sre-observability is an agent published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 15d ago), licensed MIT. It adds 75 tokens to every session and 383 once invoked, about $0.0004 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 agents, from other repositories
generate_agent
Generates a customized agent based on user-defined parameters.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…