Ongrid is an operations AI agent that investigates infrastructure problems by correlating metrics, logs, traces, topology, and alerts, then can carry out remote actions. SRE and DevOps teams use it through Slack, Telegram, Lark, DingTalk, and other supported chat channels to diagnose systems and manage Kubernetes resources. The catalogue entries provide agents, skills, and instructions for operating Ongrid.
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.
git clone --depth 1 https://github.com/ongridio/ongridWrote 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/ongridio/ongrid/incident-investigator)<a href="https://agentmods.dev/agents/ongridio/ongrid/incident-investigator"><img src="https://agentmods.dev/badge/agents/ongridio/ongrid/incident-investigator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ongridio/ongrid/incident-investigator"><img src="https://agentmods.dev/badge/agents/ongridio/ongrid/incident-investigator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.02030 |
| Opus 5 | $0.00017 | $0.01015 |
| Sonnet 5 | $0.00007 | $0.00406 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
incident-investigator 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 13d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 13d ago First seen · 121 lines · 35 tokens per session scan A a046c9f92ccf
incident-investigator is an agent published in the GitHub repository ongridio/ongrid (1,027 stars, last pushed yesterday), licensed AGPL-3.0. It adds 35 tokens to every session and 2,030 once invoked, about $0.0002 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 agents, from other repositories
grafana-expert
Builds Grafana dashboards and alerting pipelines, aligning metrics with SLOs and operational reporting.
prometheus-expert
Designs Prometheus scraping, alerting rules, and dashboards aligned with operational SLOs.
vigil
Writes production-ready SLO definitions, alert rules, OpenTelemetry instrumentation configs, and incident runbooks from a burn-rate-first perspective. Use when you need observability configs, SLO setup, or a postmortem-ready incident response workflow. Trigger with "set up my SLOs", "write my alert runbook".
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.