Is chaos-experiment safe to install?

SaferSkills independently audited chaos-experiment (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/chaos-experiment/SKILL.md · 1 file

skills/chaos-experiment/SKILL.md3.7 KB · Markdown

name: chaos-experiment

description: 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.

metadata:

author: Harness

version: 2.0.0

mcp-server: harness-mcp-v2

license: Apache-2.0

compatibility: Requires Harness MCP v2 server (harness-mcp-v2)

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: "<organization>"
  project_id: "<project>"

Step 2: Browse Templates

Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment_template"
  org_id: "<organization>"
  project_id: "<project>"

Step 3: List Existing Experiments

Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment"
  org_id: "<organization>"
  project_id: "<project>"

Step 4: Create Experiment

Call MCP tool: harness_create
Parameters:
  resource_type: "chaos_experiment"
  org_id: "<organization>"
  project_id: "<project>"
  body: <experiment definition>

Step 5: Run Experiment

Call MCP tool: harness_execute
Parameters:
  resource_type: "chaos_experiment"
  action: "run"
  resource_id: "<experiment_id>"
  org_id: "<organization>"
  project_id: "<project>"

Step 6: Monitor Results

Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_experiment_run"
  org_id: "<organization>"
  project_id: "<project>"

Get specific run details:

Call MCP tool: harness_get
Parameters:
  resource_type: "chaos_experiment_run"
  resource_id: "<run_id>"

Step 7: Check Probes

Call MCP tool: harness_list
Parameters:
  resource_type: "chaos_probe"
  org_id: "<organization>"
  project_id: "<project>"

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.

chaos-experiment— agent skill

Is chaos-experiment safe to install?

Chaos Experiment

Instructions

Step 1: Check Infrastructure

Step 2: Browse Templates

Step 3: List Existing Experiments

Step 4: Create Experiment

Step 5: Run Experiment

Step 6: Monitor Results

Step 7: Check Probes

Common Experiment Types

Chaos Resource Types

Examples

Performance Notes

Troubleshooting

Experiment Won't Run

Probes Failing

Audit the pieces. Scan the whole. Decide.