chaos-observability-integration

chaos-observability-integration is a skill for Claude Code from dungnotnull/hybrid-harness-chaos-process-prm. It costs 90 tokens per session (2,917 once invoked), scanned A, original, MIT.

A setup for monitoring chaos engineering experiments, including dashboards, metrics, alerts, and health checks. Chaos engineering deliberately introduces failures to test whether a system recovers correctly.

In plain words
What is it for?
Use it to create Grafana dashboards, Prometheus alert rules, and checks for service health during chaos experiments.
Why use it?
It makes experiment effects visible and connects failure tests to measurable signals, so you can tell what happened during a run.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the hybrid-harness-chaos-process plugin — 37 skills, 4 commands shipped together

Good fit Use it to create Grafana dashboards, Prometheus alert rules, and checks for service health during chaos experiments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration
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 dungnotnull/hybrid-harness-chaos-process-prm --skill s22-observability-integration
Clone the repo
git clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prm

Made for: Claude Code.

Or install hybrid-harness-chaos-process, the plugin that ships this one along with the rest of its 37 skills, 4 commands.

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 chaos-observability-integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration/github.svg)](https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration)
Your own site
<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration/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 chaos-observability-integration

Your own site · 80×15
<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s22-observability-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,917 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00090 $0.02917
Opus 5 $0.00045 $0.01458
Sonnet 5 $0.00018 $0.00583
Haiku 4.5 $0.00009 $0.00292

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

Security

Grade A, and why

chaos-observability-integration scanned grade A with 1 finding 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.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST http://grafana.company.com/api/dashboards/db \
skills/s22-observability-integration/SKILL.md · 394 lines

How it starts

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

Chaos Observability Integration (s20)

Purpose

Establish comprehensive observability for chaos experiments — ensuring every fault is visible, every probe is connected to real metrics, and every team member can see what's happening in real-time during chaos runs.


Prerequisites

  • Continuous verification config from s21 (CV Verification)
  • Chaos experiment results from s14-s19
  • Prometheus and Grafana deployed and accessible
  • Service metrics endpoints available
  • Dashboard creation permissions in Grafana

Input Contract

Input Source Required
Steady state metrics definitions s15 output Yes
Experiment manifests (probe configs) s12-s17 outputs Yes
Observability tool preferences s02 taste (observability) Yes
Alert routing preferences s02 taste or s01 Yes
CV verification config s19 output No

Output Contract

Output Destination Format
Chaos Grafana dashboard JSON .commandcode/artifacts/dashboard-chaos.json JSON
Prometheus alert rules for chaos .commandcode/artifacts/alerts-chaos.yaml YAML
Observability health check script .commandcode/artifacts/obs-check.sh Bash
Probe validation report s18 (game day) Markdown
Chaos metrics feed s21 (alerting), s24 (scoring) Prometheus queries

Chaos Observability Stack

Experiment Runner (LitmusChaos/HCE)
    │  Exposes chaos metrics on :8080/metrics
    ▼
Prometheus (scrapes every 15s)
    │
    ├── Grafana Dashboard (real-time chaos view)
    ├── AlertManager (chaos-specific alert rules)
    └── S24 Scoring Engine (resilience calculation)

Step 1 — Chaos Grafana Dashboard

{
  "dashboard": {
    "title": "Chaos Engineering — <SERVICE>",
    "uid": "chaos-<service>",
    "tags": ["chaos", "resilience", "<service>"],
    "timezone": "browser",
    "panels": [
      {
        "title": "Chaos Experiment Status",
        "type": "stat",
        "targets": [{
          "expr": "litmuschaos_experiment_verdict{app='<SERVICE>'}",
          "legendFormat": "{{experiment_name}}"
        }],
        "fieldConfig": {
          "defaults": {
            "mappings": [
              {"type": "value", "value": "0", "text": "Passed"},
              {"type": "value", "value": "1", "text": "Failed"}
            ],
            "thresholds": {
              "mode": "absolute",
              "steps": [
                {"color": "green", "value": null},
                {"color": "red", "value": 1}
              ]
            }
          }
        }
      },
      {
        "title": "Resilience Score (Real-time)",
        "type": "gauge",
        "targets": [{
          "expr": "litmuschaos_resilience_score{app='<SERVICE>'}"
        }],
        "fieldConfig": {
          "defaults": {
            "min": 0, "max": 100,
            "thresholds": {
              "steps": [
                {"color": "red", "value": null},
                {"color": "yellow", "value": 60},
                {"color": "green", "value": 80}
              ]
            }
          }
        }
      },
      {
        "title": "Error Rate During Chaos",
        "type": "timeseries",
        "targets": [
          {
            "expr": "sum(rate(http_requests_total{namespace='<NAMESPACE>',status=~'5..'}[1m])) / sum(rate(http_requests_total{namespace='<NAMESPACE>'}[1m])) * 100",
            "legendFormat": "Error Rate %"
          },
          {
            "expr": "5",
            "legendFormat": "Threshold (5%)"
          }
        ],
        "fieldConfig": {
          "defaults": {
            "thresholds": {
              "steps": [
                {"color": "green", "value": null},
                {"color": "red", "value": 5}
              ]
            }
          }
        }
      },
      {
        "title": "P99 Latency During Chaos",
        "type": "timeseries",
        "targets": [{
          "expr": "histogram_quantile(0.99, sum(rate(http_request_duration_ms_bucket{namespace='<NAMESPACE>'}[1m])) by (le))",
          "legendFormat": "P99 (ms)"
        }]
      },
      {
        "title": "Pod Status During Chaos",
        "type": "stat",
        "targets": [
          {
            "expr": "count(kube_pod_status_ready{namespace='<NAMESPACE>', condition='true'})",
            "legendFormat": "Ready"
          },
          {
            "expr": "count(kube_pod_status_ready{namespace='<NAMESPACE>', condition='false'})",
            "legendFormat": "Not Ready"
          }
        ]
      },
      {
        "title": "Active Faults",
        "type": "table",
        "targets": [{
          "expr": "litmuschaos_active_experiments{namespace='<NAMESPACE>'}",
          "format": "table"
        }]
      },
      {
        "title": "Probe Status",
        "type": "status-history",
        "targets": [{
          "expr": "litmuschaos_probe_success_total{namespace='<NAMESPACE>'}",
          "legendFormat": "{{probe_name}}"
        }]
      }
    ]
  }
}

Read the full file on GitHub · 394 lines

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 · 394 lines · 90 tokens per session scan A 3b0a79de6c54

Subscribe to this mod's changes

chaos-observability-integration is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 2,917 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens