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.
npx skills add shenli/distributed-system-testing --skill executing-distributed-system-testsgit clone --depth 1 https://github.com/shenli/distributed-system-testingWrote 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.
[](https://agentmods.dev/skills/shenli/distributed-system-testing/executing-distributed-system-tests)<a href="https://agentmods.dev/skills/shenli/distributed-system-testing/executing-distributed-system-tests"><img src="https://agentmods.dev/badge/skills/shenli/distributed-system-testing/executing-distributed-system-tests/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.
<a href="https://agentmods.dev/skills/shenli/distributed-system-testing/executing-distributed-system-tests"><img src="https://agentmods.dev/badge/skills/shenli/distributed-system-testing/executing-distributed-system-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 56 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00218 | $0.04754 |
| Opus 5.5 | $0.00087 | $0.01902 |
| Sonnet 5.5 | $0.00044 | $0.00951 |
| Haiku 4.5 | $0.00022 | $0.00475 |
Grade A, and why
executing-distributed-system-tests scanned grade A with 2 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 2mo 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
already know whether they have Docker, sudo for iptables, a Go Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
output file, `docker compose ps`, `curl` a health endpoint) every How it starts
The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Distributed-System Tests
Pairs with designing-distributed-system-tests. That skill produces
a plan; this skill runs it. The two communicate only through
filesystem artifacts: the plan file in and a session directory
plus findings report out.
The most common failure mode this skill is built to avoid: a run that produces a green checkmark without anyone having checked that the workload, the fault, and the oracle each did their job. The "green-but-broken" checks are not optional.
Process
1. Load the plan
If a plan file path was supplied, read it. If the user described a plan in conversation, extract the scenario list. If the plan is missing oracles or per-scenario budget tiers (Smoke / Hardening / Release, per the plan template's §7 scenario fields), halt — hand back to the design skill rather than improvise. Improvising an oracle in the moment is how green-but-broken results get produced.
2. Discover the SUT toolbox
Search the repo before writing any new code. Look for:
tools/,scripts/,bin/— drivers, workload generators, cluster bring-up scriptstests/integration/,tests/stability/,tests/chaos/docs/runbooks/,docs/testing/,docs/stability-test-plan.md- Makefile / justfile /
cargo xtasktargets that look like cluster commands - existing CI definitions that already wire fault-injection
Record what you found in the session log under "Toolbox discovered". This is required before any scenario runs — it prevents the skill from re-inventing tools that already exist.
2b. Probe environment capability and guide install if needed
Right after toolbox discovery, before running any scenario, check that the host can actually run the toolbox you just catalogued. If the plan has an "Environment requirements" section (the design skill emits one), treat it as the spec; otherwise infer the list from the selected techniques and the SUT toolbox.
Ask the user first; do not silently probe. Before running any
which / --version / docker ps checks, list the capabilities
the plan needs and ask the user: "what's available in your
environment, and what would you like me to skip?" Most operators
already know whether they have Docker, sudo for iptables, a Go
toolchain, etc. Asking up front saves a probe round, surfaces
substitution options the operator may know about (e.g. "I have
podman instead of Docker"), and respects their authority over
their own machine. After the user answers, verify with quick
probes and reconcile any gap between what they said and what's
actually present.
What ships with it
8 files beside SKILL.md 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.
- assets/findings-report-template.md 8.6 KB
- assets/session-log-template.md 2.2 KB
- references/fault-injection-howto.md 6.1 KB
- references/finding-classification.md 2.2 KB
- references/green-but-broken-red-flags.md 5.0 KB
- references/oracle-patterns.md 10 KB
- references/test-case-reduction.md 3.6 KB
- references/verdict-taxonomy.md 8.1 KB
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.
- 2mo ago First seen · 412 lines · 218 tokens per session scan A 2608781314b4
executing-distributed-system-tests is a skill published in the GitHub repository shenli/distributed-system-testing (231 stars, last pushed 3mo ago), licensed MIT. It adds 218 tokens to every session and 4,754 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chaos-engineering-resilience
Chaos engineering principles, controlled failure injection, resilience testing, and system recovery validation. Use when testing distributed systems, building confidence in fault tolerance, or validating disaster recovery.
agent-resilience-testing
Orchestrates end-to-end resilience testing for LLM agents with AgentBreak, including LLM infrastructure failures, prompt injection, agent skill supply-chain risk, guardrail verification, and MCP server/tool failures. Use when the user asks to "test my agent for resilience", "chaos test this agent", "find failure modes…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.