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.
npx skills add ongridio/ongrid --skill ongrid-alert-triagegit 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/skills/ongridio/ongrid/ongrid-alert-triage)<a href="https://agentmods.dev/skills/ongridio/ongrid/ongrid-alert-triage"><img src="https://agentmods.dev/badge/skills/ongridio/ongrid/ongrid-alert-triage/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/skills/ongridio/ongrid/ongrid-alert-triage"><img src="https://agentmods.dev/badge/skills/ongridio/ongrid/ongrid-alert-triage.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.00040 | $0.00479 |
| Opus 5.5 | $0.00016 | $0.00192 |
| Sonnet 5.5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
ongrid-alert-triage 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 5d 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.
- 5d ago First seen · 19 lines · 40 tokens per session scan A 705801f4826b
ongrid-alert-triage is a skill published in the GitHub repository ongridio/ongrid (1,255 stars, last pushed yesterday), licensed AGPL-3.0. It adds 40 tokens to every session and 479 once invoked, about $0.0002 per session on Opus 5.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-10-31.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
investigating-incidents-with-runbooks
Investigate an incident with organization-owned runbook guidance, loaded by URL or exact alert identity. Multi-step; load before acting.
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
summarizing-sentry-issues
Summarise Sentry issues by theme and impact with optional uptime rollup. For overviews, morning digests, reliability questions.
k8s-monitoring-alerting
A Kubernetes diagnostic and repair method for Prometheus and Grafana monitoring problems, including alerts that do not trigger. Prometheus collects measurements, while Grafana displays them in dashboards.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.