distributed-system-testing

A plugin containing two connected skills for designing and running Jepsen-style tests on distributed and stateful systems. These tests deliberately introduce failures and check whether data remains correct.

In plain words
What is it for?
Use it to create and execute test plans involving fault injection, chaos scenarios, linearizability checks, partitions, crashes, upgrades, and other distributed-system conditions.
Why use it?
It provides a structured way to test claims about reliability, consistency, recovery, and behavior during faults instead of relying only on normal-case tests.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add shenli/distributed-system-testing
agentmods
npx agentmods add plugins/shenli/distributed-system-testing/distributed-system-testing
Clone the repo
git clone --depth 1 https://github.com/shenli/distributed-system-testing

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

distributed-system-testing 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 2d 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.

.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "distributed-testing-skills",
  "version": "0.1.0",
  "description": "Two coupled skills that design and execute claim-driven, Jepsen-style test plans for distributed and stateful systems.",
  "author": {
    "name": "Li Shen"
  },
  "homepage": "https://github.com/shenli/distributed-system-testing",
  "repository": "https://github.com/shenli/distributed-system-testing",
  "license": "MIT",
  "keywords": [
    "distributed-systems",
    "testing",
    "jepsen",
    "chaos-engineering",
    "fault-injection",
    "linearizability"
  ]
}
Files

What ships with it

1 file beside plugin.json 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.

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. 2d ago First seen · 20 lines scan A a3dec8f8a052

Subscribe to this mod's changes

distributed-system-testing is a plugin published in the GitHub repository shenli/distributed-system-testing (228 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.