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 johnqtcg/awesome-skills --skill monitoring-alertinggit clone --depth 1 https://github.com/johnqtcg/awesome-skillsWrote 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/johnqtcg/awesome-skills/monitoring-alerting)<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.
<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>- NVIDIA SkillSpector pass
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.00137 | $0.05910 |
| Opus 5.5 | $0.00055 | $0.02364 |
| Sonnet 5.5 | $0.00027 | $0.01182 |
| Haiku 4.5 | $0.00014 | $0.00591 |
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 1mo 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.
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,
forduration, 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
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.
- references/alert-anti-patterns.md 10.0 KB
- references/alertmanager-config-patterns.md 7.7 KB
- references/sli-slo-patterns.md 21 KB
- scripts/eval_forward.py 25 KB runs code
- scripts/gen_toc.py 4.9 KB runs code
- scripts/lint_monitoring_docs.py 46 KB runs code
- scripts/run_regression.sh 4.3 KB runs code
- scripts/tests/COVERAGE.md 22 KB
- scripts/tests/golden/001_no_sli.json 1.1 KB
- scripts/tests/golden/002_non_actionable.json 1.1 KB
- scripts/tests/golden/003_severity_mismatch.json 1.1 KB
- scripts/tests/golden/004_no_for_duration.json 1009 B
- scripts/tests/golden/005_no_runbook.json 1.1 KB
- scripts/tests/golden/006_high_cardinality.json 1016 B
- scripts/tests/golden/007_well_formed_slo.json 4.0 KB
- scripts/tests/golden/008_good_dashboard.json 1.2 KB
- scripts/tests/golden/009_degraded_no_context.json 1.0 KB
- scripts/tests/golden/010_greenfield_design.json 1.2 KB
- scripts/tests/golden/011_no_grouping.json 1.2 KB
- scripts/tests/golden/012_no_inhibition_rules.json 1.7 KB
- scripts/tests/golden/013_error_budget_exhaustion.json 3.3 KB
- scripts/tests/golden/014_up_zero_severity.json 2.3 KB
- scripts/tests/golden/015_up_zero_unknown_topology.json 1.5 KB
- scripts/tests/golden/016_latency_slo_request.json 1.7 KB
- scripts/tests/test_golden_scenarios.py 18 KB runs code
- scripts/tests/test_lint_mutations.py 15 KB runs code
- scripts/tests/test_skill_contract.py 8.0 KB runs code
- scripts/tests/test_yaml_artifacts.py 29 KB runs code
- tests/eval/RESULTS.md 7.8 KB
- tests/promtool/rules_test.yml 7.2 KB
- tests/promtool/rules.yml 2.5 KB
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.
- 1mo ago First seen · 385 lines · 137 tokens per session scan A ca503f7034a7
monitoring-alerting is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed 17d ago), licensed MIT. It adds 137 tokens to every session and 5,910 once invoked, about $0.0005 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.
Other skills, from other repositories
aws-architect
Design AWS architectures — VPCs, EC2, ECS, Lambda, RDS, S3, CloudFront, and Well-Architected Framework reviews.
azure-architect
Design Azure architectures — AKS, Functions, Cosmos DB, Service Bus, and Azure AD integration patterns.
gcp-architect
Design Google Cloud architectures — GKE, Cloud Run, BigQuery, Pub/Sub, and Cloud Spanner solutions.
n8n-workflow
Build n8n automation workflows — nodes, expressions, error handling, and self-hosted deployment.
terraform-writer
Write Terraform infrastructure-as-code — providers, modules, state management, and cloud resource definitions.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.