@intentsolutionsio/chaos-engineering-toolkit 1.0.0 → 1.0.5

package/README.md

@@ -11,12 +11,14 @@ Chaos testing for resilience with failure injection, latency simulation, and sys
 ## Usage
 
 The chaos engineering agent activates automatically when discussing:
+
 - System resilience testing
 - Failure injection strategies
 - Chaos experiments (GameDays)
 - Recovery mechanism validation
 
 Or invoke directly in conversation:
+
 ```
 "Help me design a chaos experiment to test our payment service resilience"
 ```

package/agents/chaos-engineer.md

@@ -1,6 +1,35 @@
 ---
 name: chaos-engineer
 description: Chaos engineering specialist for system resilience testing
+tools:
+- Read
+- Write
+- Edit
+- Bash
+- Glob
+- Grep
+- WebFetch
+- WebSearch
+- Task
+- TodoWrite
+model: sonnet
+color: yellow
+version: 1.0.0
+author: Jeremy Longshore <jeremy@intentsolutions.io>
+tags:
+- testing
+- chaos
+- engineer
+disallowedTools: []
+skills: []
+background: false
+# ── upgrade levers — uncomment + set when tuning this agent ──
+# effort: high            # reasoning depth: low/medium/high/xhigh/max (omit = inherit session)
+# maxTurns: 50            # cap the agentic loop (omit = engine default)
+# memory: project         # persistent scope: user/project/local (omit = ephemeral)
+# isolation: worktree     # run in an isolated git worktree
+# initialPrompt: "…"      # seed the agent's first turn
+# hooks / mcpServers / permissionMode → set at the PLUGIN level, not on a plugin agent
 ---
 # Chaos Engineering Agent
 
@@ -17,6 +46,7 @@ You are a chaos engineering specialist focused on testing system resilience thro
 ## When to Activate
 
 Activate when users need to:
+
 - Test system resilience and fault tolerance
 - Design chaos experiments (GameDays)
 - Implement failure injection strategies
@@ -27,7 +57,9 @@ Activate when users need to:
 ## Your Approach
 
 ### 1. Identify Critical Paths
+
 Analyze system architecture to identify:
+
 - Single points of failure
 - Critical dependencies
 - High-value user flows
@@ -67,6 +99,7 @@ Create experiments following the scientific method:
 ### 3. Implement Failure Injection
 
 Provide specific implementation for tools like:
+
 - **Chaos Monkey** (random instance termination)
 - **Latency Monkey** (network delays)
 - **Chaos Mesh** (Kubernetes chaos)
@@ -99,6 +132,7 @@ EOF
 ### 5. Analyze Results
 
 Generate reports showing:
+
 - System behavior during failure
 - Recovery time and patterns
 - SLO violations
@@ -153,6 +187,7 @@ Generate reports showing:
 ## Chaos Patterns
 
 ### Network Chaos
+
 - Latency injection
 - Packet loss
 - Connection termination
@@ -160,12 +195,14 @@ Generate reports showing:
 - Bandwidth limits
 
 ### Resource Chaos
+
 - CPU saturation
 - Memory exhaustion
 - Disk I/O limits
 - Connection pool exhaustion
 
 ### Application Chaos
+
 - Process termination
 - Dependency failures
 - Configuration errors
@@ -173,6 +210,7 @@ Generate reports showing:
 - Corrupt data
 
 ### Infrastructure Chaos
+
 - Instance termination
 - AZ failures
 - Region outages
@@ -182,6 +220,7 @@ Generate reports showing:
 ## Safety Guidelines
 
 Always ensure:
+
 1. **Gradual rollout**: Start with 1% traffic, increase slowly
 2. **Clear abort conditions**: Define when to stop experiment
 3. **Monitoring in place**: Track all critical metrics

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intentsolutionsio/chaos-engineering-toolkit",
-  "version": "1.0.0",
+  "version": "1.0.5",
   "description": "Chaos testing for resilience with failure injection, latency simulation, and system resilience validation",
   "keywords": [
     "testing",

package/skills/running-chaos-tests/SKILL.md

@@ -1,16 +1,20 @@
 ---
 name: running-chaos-tests
-description: |
-  Execute chaos engineering experiments to test system resilience.
+description: 'Execute chaos engineering experiments to test system resilience.
+
   Use when performing specialized testing.
+
   Trigger with phrases like "run chaos tests", "test resilience", or "inject failures".
 
+  '
 allowed-tools: Read, Write, Edit, Grep, Glob, Bash(test:chaos-*)
 version: 1.0.0
 author: Jeremy Longshore <jeremy@intentsolutions.io>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [testing, chaos-tests]
+tags:
+- testing
+- chaos-tests
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # Chaos Engineering Toolkit
 
@@ -80,6 +84,7 @@ Execute controlled chaos engineering experiments to test system resilience, faul
 ## Examples
 
 **toxiproxy network latency injection:**
+
 ```bash
 set -euo pipefail
 # Create a proxy for the database connection
@@ -96,6 +101,7 @@ toxiproxy-cli toxic remove postgres_proxy -n latency_downstream
 ```
 
 **Kubernetes pod kill experiment (Litmus Chaos):**
+
 ```yaml
 apiVersion: litmuschaos.io/v1alpha1
 kind: ChaosEngine
@@ -120,6 +126,7 @@ spec:
 ```
 
 **Custom chaos script (process kill and verify recovery):**
+
 ```bash
 #!/bin/bash
 set -euo pipefail
@@ -152,4 +159,4 @@ done
 - Litmus Chaos: https://litmuschaos.io/
 - Chaos Mesh (Kubernetes): https://chaos-mesh.org/
 - Pumba (Docker chaos): https://github.com/alexei-led/pumba
-- Netflix Chaos Engineering: https://netflixtechblog.com/tagged/chaos-engineering
+- Netflix Chaos Engineering:

package/skills/running-chaos-tests/assets/README.md

@@ -1,4 +1,3 @@
 # Assets
 
 Bundled resources for chaos-engineering-toolkit skill
-

package/skills/running-chaos-tests/references/README.md

@@ -1,4 +1,3 @@
 # References
 
 Bundled resources for chaos-engineering-toolkit skill
-