monitoring-setup

monitoring-setup is a skill for Claude Code, Codex from inbharatai/claude-skills. It costs 33 tokens per session (410 once invoked), scanned A, original, MIT.

A setup guide for observability, the practice of understanding a running system through its metrics, dashboards, alerts, and operating procedures. It covers Prometheus, Grafana, alert rules, service targets, error budgets, and on-call runbooks.

In plain words
What is it for?
Use it to configure monitoring dashboards, define alerts and reliability targets, track error budgets, and write on-call instructions.
Why use it?
It helps teams notice failures, measure service reliability, and know how to respond when systems degrade.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to configure monitoring dashboards, define alerts and reliability targets, track error budgets, and write on-call instructions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/inbharatai/claude-skills/monitoring-setup
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 inbharatai/claude-skills --skill monitoring-setup
Clone the repo
git clone --depth 1 https://github.com/inbharatai/claude-skills

Made for: Claude Code, Codex.

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-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/inbharatai/claude-skills/monitoring-setup"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/monitoring-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 410 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.
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.00033 $0.00410
Opus 5 $0.00016 $0.00205
Sonnet 5 $0.00007 $0.00082
Haiku 4.5 $0.00003 $0.00041

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

Security

Grade A, and why

monitoring-setup 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 9d 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.

skills/monitoring-setup/SKILL.md · 68 lines

What it actually says

Monitoring Setup

Overview

Configure observability stacks — Prometheus, Grafana, alerting rules, SLOs, error budgets, and on-call runbooks.

When to Use This Skill

Use Monitoring Setup when you need to:

  • Work with monitoring setup tasks in your project or workflow
  • Automate monitoring setup operations at scale
  • Generate production-quality monitoring setup output quickly

Instructions

When this skill is active, Claude will:

  1. Understand the full context of your monitoring setup request
  2. Apply best practices and conventions for DevOps & Infrastructure
  3. Produce clean, well-structured, production-ready output
  4. Explain key decisions and offer alternatives where relevant

Examples

Example 1 — Basic Usage

User: Help me get started with monitoring setup.

Claude: I'll walk you through the essential steps for monitoring setup in your context...

Example 2 — Advanced Usage

User: I need a production-ready monitoring setup setup with full error handling.

Claude: Here's a complete, production-hardened monitoring setup implementation...

Guidelines

  • Always validate inputs before processing
  • Follow the conventions of the target platform or language
  • Prefer explicit over implicit — clarity beats cleverness
  • Include comments for non-obvious logic
  • Suggest tests or validation steps where appropriate

Dependencies

Required: prometheus, grafana

Platforms

Available on: claude-code, api


Part of the claude-skills collection — 183+ skills for Claude.

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. 9d ago First seen · 68 lines · 33 tokens per session scan A 9281312b9bd0

Subscribe to this mod's changes

monitoring-setup is a skill published in the GitHub repository inbharatai/claude-skills (33 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 410 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-09-03.

Related

Other skills, from other repositories

human-review

Produce a plain-English review of the files you just edited and gate the changes behind an explicit Approve/Undo choice. Use when the Stop hook from the human-review-skill plugin asks for a review (you'll see a prompt referencing an edit log), OR when the developer's most recent message is "1", "2", "approve", or…

IrtezaAsadRizvi/claude-human-review · 83 tokens

optimize

Automatically refines every user prompt into a structured, actionable version, then immediately executes the optimized prompt. When triggered explicitly with "/optimize {prompt}", "optimize:", or "optimize prompt:", outputs the refined prompt as text instead.

Hashaam101/prompt-optimizer · 51 tokens

mysql-migration

MySQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning MySQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, charset conversions, data backfills, or any DDL touching production tables. Covers online DDL algorithm selection (INSTANT/INPLACE/COPY)…

johnqtcg/awesome-skills · 132 tokens

redis-cache-strategy

Redis caching strategy designer and reviewer. ALWAYS use when designing, reviewing, or troubleshooting Redis caching layers — cache pattern selection (cache-aside, write-through, write-behind), TTL strategy, cache stampede/penetration/avalanche prevention, hot key handling, cache-DB consistency, distributed locking…

johnqtcg/awesome-skills · 113 tokens

systematic-debugging

Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.

johnqtcg/awesome-skills · 49 tokens

google-search

Use when the user wants help finding information through Google or Google-style web search and expects more than raw links. Handle current facts, public-information lookups, official documents, tutorials, reports, tools, materials, or source discovery by classifying the search goal, generating precise queries…

johnqtcg/awesome-skills · 107 tokens