# Chaos Experiment

> Create and manage chaos experiments using Harness Chaos Engineering via MCP. Run resilience tests like pod deletion, CPU stress, and network faults. Use when user says "chaos experiment", "chaos engineering", "resilience test", "chaos test", or wants to test system reliability.

- **Type:** Skill
- **Install:** `agentstack add skill-harness-harness-skills-chaos-experiment`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [harness](https://agentstack.voostack.com/s/harness)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [harness](https://github.com/harness)
- **Source:** https://github.com/harness/harness-skills/tree/main/skills/chaos-experiment
- **Website:** https://developer.harness.io/docs/platform/harness-ai/harness-skills/

## Install

```sh
agentstack add skill-harness-harness-skills-chaos-experiment
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Chaos Experiment

Create and manage chaos experiments using Harness Chaos Engineering via MCP.

## Instructions

### Step 1: Check Infrastructure

```
Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_infrastructure"
  org_id: ""
  project_id: ""
```

### Step 2: Browse Templates

```
Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment_template"
  org_id: ""
  project_id: ""
```

### Step 3: List Existing Experiments

```
Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment"
  org_id: ""
  project_id: ""
```

### Step 4: Create Experiment

```
Call MCP tool: harness_create
Parameters:
  resource_type: "chaos_experiment"
  org_id: ""
  project_id: ""
  body: 
```

### Step 5: Run Experiment

```
Call MCP tool: harness_execute
Parameters:
  resource_type: "chaos_experiment"
  action: "run"
  resource_id: ""
  org_id: ""
  project_id: ""
```

### Step 6: Monitor Results

```
Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment_run"
  org_id: ""
  project_id: ""
```

Get specific run details:

```
Call MCP tool: harness_get
Parameters:
  resource_type: "chaos_experiment_run"
  resource_id: ""
```

### Step 7: Check Probes

```
Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_probe"
  org_id: ""
  project_id: ""
```

## Common Experiment Types

- **Pod Delete** - Kill pods to test recovery
- **Pod CPU Hog** - Stress CPU to test throttling
- **Pod Memory Hog** - Consume memory to test OOM handling
- **Pod Network Loss** - Simulate network failures
- **Pod Network Latency** - Add artificial latency
- **Node Drain** - Drain K8s nodes
- **EC2 Stop** - Stop AWS EC2 instances
- **ECS Task Stop** - Stop ECS tasks

## Chaos Resource Types

| Resource Type | Operations | Description |
|--------------|-----------|-------------|
| `chaos_experiment` | list, get, create, update, delete, run | Experiments |
| `chaos_experiment_run` | list, get | Run history/results |
| `chaos_experiment_template` | list, get | Pre-built templates |
| `chaos_infrastructure` | list, get | Target infrastructure |
| `chaos_probe` | list, get | Health probes |

## Examples

- "Show me all chaos experiments" - List chaos_experiment
- "Create a pod-delete experiment for checkout-service" - Create chaos_experiment
- "Run the weekly resilience test" - Execute run action
- "What were the results of the last chaos run?" - Get chaos_experiment_run

## Performance Notes

- Review existing experiments before creating duplicates. Check for similar fault types targeting the same service.
- Wait for experiment completion before analyzing results. Do not draw conclusions from partial runs.
- Verify the target infrastructure and service are healthy before running chaos experiments.

## Troubleshooting

### Experiment Won't Run
- Verify chaos infrastructure is connected and active
- Check target application/namespace exists
- Ensure RBAC permissions for chaos operations

### Probes Failing
- Check probe endpoints are accessible
- Verify probe timeout settings
- Review probe type matches expected behavior

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [harness](https://github.com/harness)
- **Source:** [harness/harness-skills](https://github.com/harness/harness-skills)
- **License:** Apache-2.0
- **Homepage:** https://developer.harness.io/docs/platform/harness-ai/harness-skills/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-harness-harness-skills-chaos-experiment
- Seller: https://agentstack.voostack.com/s/harness
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.