agentmods.dev

monitoring-alerting

monitoring-alerting is a skill for Claude Code from johnqtcg/awesome-skills. It costs 137 tokens per session (5,910 once invoked), scanned A, original, MIT.

A review guide for monitoring and alerting in production backend services. It covers service health measures, Prometheus rules, Grafana dashboards, and routing alerts to tools such as PagerDuty, Opsgenie, or Slack.

In plain words
What is it for?
Use it to define SLIs and SLOs, set error budgets and burn-rate alerts, review Prometheus rules and Grafana dashboards, and check alert routing and grouping.
Why use it?
It helps catch unclear, noisy, or incomplete monitoring designs before they make incidents harder to detect or respond to.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 30repo today A scan SkillSpector: pass 137 tokens original MIT

Good fit Use it to define SLIs and SLOs, set error budgets and burn-rate alerts, review Prometheus rules and Grafana dashboards, and check alert routing and grouping.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/johnqtcg/awesome-skills/monitoring-alerting
View source ↗ johnqtcg/awesome-skills johnqtcg.github.io
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 johnqtcg/awesome-skills --skill monitoring-alerting
Clone the repo
git clone --depth 1 https://github.com/johnqtcg/awesome-skills

Made for: Claude Code.

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 monitoring-alerting

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/monitoring-alerting"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/monitoring-alerting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,910 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.00137 $0.05910
Opus 5 $0.00068 $0.02955
Sonnet 5 $0.00027 $0.01182
Haiku 4.5 $0.00014 $0.00591

Measured 11d ago against content hash ca503f7034a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

monitoring-alerting 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 11d ago.

The scan reads SKILL.md. This mod also ships 8 executable files (scripts/eval_forward.py, scripts/gen_toc.py, scripts/lint_monitoring_docs.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/monitoring-alerting/SKILL.md · 385 lines

How it starts

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

Monitoring & Alerting Design Review

Quick Reference

If you need to… Go to
Scope / prerequisites / depth §1, §2 Gates, §3 Depth
Handle incomplete context §4 Degradation Modes
Evaluate the design item by item §5 Design Checklist
Validate rules before shipping §5.5 Rule Validation
Avoid common alerting mistakes §6 Anti-Examples
Score, then format the output §7 Scorecard, §8 Output Contract
SLI/SLO, burn-rate, error budget references/sli-slo-patterns.md
Alert anti-patterns and fatigue references/alert-anti-patterns.md
Routing / grouping / inhibition config references/alertmanager-config-patterns.md

§1 Scope

In scope — monitoring and alerting for production backend services:

  • SLI (Service Level Indicator) definition and measurement
  • SLO (Service Level Objective) target setting and error budget
  • Prometheus alerting rules (PromQL, for duration, severity labels)
  • Burn-rate alerting (multi-window, multi-burn-rate SLO alerts)
  • Grafana dashboard design (layout, variable templating, panel types)
  • Alert routing configuration (PagerDuty/OpsGenie/Slack, severity-based routing)
  • Alert fatigue audit (noise ratio, actionability, deduplication)
  • Label cardinality management (high-cardinality label detection)
  • On-call runbook integration (alert → runbook → action mapping)

Out of scope — delegate to dedicated skills:

  • Metrics/tracing instrumentation in code → go-observability-review
  • Application performance profiling → go-benchmark
  • Infrastructure provisioning (Prometheus/Grafana setup) → ops tooling
  • Log aggregation pipeline design → separate skill

Read the full file on GitHub · 385 lines

Files

What ships with it

31 files 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. 11d ago First seen · 385 lines · 137 tokens per session scan A ca503f7034a7

Subscribe to this mod's changes

monitoring-alerting is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 5,910 once invoked, about $0.0007 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.

Analytics and metricsClaude CodeCloudDevOps and cloudagentsai-assistantai-skillsanthropicdeveloper-tools
Related

Other skills, from other repositories

security-compliance

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

sangrokjung/claude-forge · 56 tokens

stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

sangrokjung/claude-forge · 30 tokens

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…

sangrokjung/claude-forge · 183 tokens

manage-skills

A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.

sangrokjung/claude-forge · 54 tokens

blind-spot-pass

Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…

sangrokjung/claude-forge · 221 tokens

skill-factory

A workflow that examines completed session work and turns reusable patterns into Claude Code skills.

sangrokjung/claude-forge · 122 tokens