investigate-alert

investigate-alert is a skill for Claude Code from grafana/gcx. It costs 59 tokens per session (1,453 once invoked), scanned A, original, Apache-2.0.

A diagnostic workflow for Grafana alerts—rules that notify you when monitored data meets a condition. It examines an alert’s state, scope, and impact to explain why it is firing or pending.

In plain words
What is it for?
Use it to investigate a named alert, inspect its rule and data, determine affected resources, and identify practical next steps.
Why use it?
It turns an alert notification into specific information about the underlying condition and whether action is needed.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin.

Part of the gcx plugin — 24 skills, 1 agent shipped together

Good fit Use it to investigate a named alert, inspect its rule and data, determine affected resources, and identify practical next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/grafana/gcx/investigate-alert
About the project

gcx is a command-line tool that lets people and AI coding agents manage and inspect Grafana Cloud, Enterprise, and open-source instances. It provides access to dashboards, alerts, SLOs, metrics, logs, and traces, with workflows for alert investigation, dashboard management, GitOps, and observability setup. Its catalogue entries provide agent instructions and extensions for using gcx.

grafana/gcx · 817 stars · on GitHub · grafana.com

Install

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.

Any agent
npx skills add grafana/gcx --skill investigate-alert
Clone the repo
git clone --depth 1 https://github.com/grafana/gcx

Made for: Claude Code.

Or install gcx, the plugin that ships this one along with the rest of its 24 skills, 1 agent.

Wrote 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.

agentmods badge for investigate-alert

README.md
[![agentmods](https://agentmods.dev/badge/skills/grafana/gcx/investigate-alert/github.svg)](https://agentmods.dev/skills/grafana/gcx/investigate-alert)
Your own site
<a href="https://agentmods.dev/skills/grafana/gcx/investigate-alert"><img src="https://agentmods.dev/badge/skills/grafana/gcx/investigate-alert/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.

agentmods 80×15 button for investigate-alert

Your own site · 80×15
<a href="https://agentmods.dev/skills/grafana/gcx/investigate-alert"><img src="https://agentmods.dev/badge/skills/grafana/gcx/investigate-alert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01453
Opus 5.5 $0.00024 $0.00581
Sonnet 5.5 $0.00012 $0.00291
Haiku 4.5 $0.00006 $0.00145

Measured 14d ago against content hash c73cf0e83845, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

investigate-alert 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 14d 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.

claude-plugin/skills/investigate-alert/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Grafana Alert Investigator

Investigate Grafana alerts by analyzing state, querying datasources, and identifying next steps. Be concise and direct - these are experienced operators who need actionable information, not hand-holding.

Core Principles

  1. Stop early for non-actionable scenarios (recording rules, healthy inactive alerts)
  2. Be concise - no fluff, no excessive formatting, no obvious advice
  3. Trust the user's expertise - no timelines, no patronizing suggestions
  4. Focus on actionable information

Prerequisites

User needs gcx installed with configured context and appropriate permissions. If gcx is not configured, use the setup-gcx skill first.

Investigation Workflow

Step 1: Verify Context and Locate Alert

Check context if needed (gcx config view). If multiple contexts exist and none specified, ask which to use.

Step 2: Get Alert Details and Check for Early Exit

Fetch the alert by listing all alerts and filtering by name. Replace <AlertName> with the actual alert name:

gcx alert rules list -o json | jq -r '.[] | .rules[]? | select(.name == "<AlertName>")'

Server-side filters (use instead of downloading all rules and filtering with jq):

  • --state firing|pending|inactive — filter by rule state
  • --group <name> — filter by group name
  • --folder <uid> — filter by folder UID

Filter by name, state, cluster/environment as relevant. If multiple matches, list them and ask which to investigate. Inform the user which context you're using.

Check the type field:

  • If type: recording: This is a recording rule, not an alerting rule. Report: "This is a recording rule (pre-calculates metrics), not an alerting rule. It doesn't fire alerts. Current state: [state]. Want details on what it's recording?" Stop here unless they ask for more.

Check the state field:

  • If state: inactive AND the alert's query looks healthy: Report: "Alert is inactive. [Brief what it monitors]. Health: [health]. Last evaluated: [time]. Want to see historical trends?" Stop here unless they ask for more.
  • If state: firing or state: pending: Continue with full investigation below.

Read the full file on GitHub · 159 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 14d ago Changed · +3 lines · -54 tokens per session c73cf0e83845
  2. 2mo ago First seen · 156 lines · 113 tokens per session scan A 0e167076c763

Subscribe to this mod's changes

investigate-alert is a skill published in the GitHub repository grafana/gcx (817 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,453 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-08-30.

Related

investigate-alert compared with skills from other repositories

investigate-alert next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
investigate-alertgrafana/gcxSkill817todayApache-2.0A59Claude Code
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skillsSkill1.9k23d agoMITA36Claude Code
diagnosing-missing-recordingsPostHog/posthogSkill41ktodaynoneA76Claude Code, Codex