dcs-test

dcs-test is a skill for Claude Code from Kevin-Liu-01/Agent-Machines. It costs 41 tokens per session (840 once invoked), scanned B, original, MIT.

A test runner for DCS, a distributed storage system, covering its control service, host agent, storage daemon, and live clusters.

In plain words
What is it for?
Use it to run unit, integration, chaos, filesystem, virtual-machine, API smoke, load, and scenario tests.
Why use it?
It provides ready-made checks for testing DCS changes locally, in CI, or against running environments.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go run ./apps/cloud/apps/dcs/src/tests/cmd/dcs-check unit.

Good fit Use it to run unit, integration, chaos, filesystem, virtual-machine, API smoke, load, and scenario tests.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Kevin-Liu-01/Agent-Machines
agentmods
npx agentmods add skills/kevin-liu-01/agent-machines/dcs-test

Made for: Claude Code.

Wrote 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.

agentmods badge for dcs-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/dcs-test/github.svg)](https://agentmods.dev/skills/kevin-liu-01/agent-machines/dcs-test)
Your own site
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/dcs-test"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/dcs-test/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.

agentmods 80×15 button for dcs-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/dcs-test"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/dcs-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 840 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00840
Opus 5 $0.00020 $0.00420
Sonnet 5 $0.00008 $0.00168
Haiku 4.5 $0.00004 $0.00084

Measured 10d ago against content hash b9bd9da730f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

dcs-test scanned grade B with 1 finding 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 10d 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 rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

pnpm dcs testbox run "sudo ./target/release/dm-check --iters 2"
knowledge/skills/dcs-test/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

  • Test hub: apps/cloud/apps/dcs/src/tests/README.md
  • Local profile runner: apps/cloud/apps/dcs/src/tests/cmd/dcs-check/
  • Live API smoke runner: apps/cloud/apps/dcs/src/tests/cmd/dcs-smoke/
  • Scenario/load runner: apps/cloud/apps/dcs/src/tests/cmd/dcs-gauntlet/
  • Remote Linux/KVM runner: pnpm dcs testbox

Profiles

Run the cheapest command that proves the changed invariant:

dcs-check unit [--scope controlplane|host-agent|storage-daemon|all]
dcs-check integration [--scope controlplane|host-agent|storage-daemon|all]
dcs-check kwok
dcs-check chaos
dcs-check chaos-compaction
dcs-check kvm
dcs-check fuse [--suite all|sanity|pjdfstest|git|npm|rust-compile|c-compile|go-compile|data-integrity|concurrent|fsstress|xfstests|xfstest-general]
dcs-check full

Live API verification:

DEDALUS_API_KEY=... dcs-smoke --env=dev
DEDALUS_API_KEY=... dcs-smoke --base https://dev.dcs.dedaluslabs.ai --iterations 2

Load and scenario drills:

DEDALUS_API_KEY=... dcs-gauntlet scale --base https://dev.dcs.dedaluslabs.ai --count 20
DEDALUS_API_KEY=... dcs-gauntlet ramp --base https://dev.dcs.dedaluslabs.ai --count 20
DEDALUS_API_KEY=... dcs-gauntlet compaction-drain --base https://dev.dcs.dedaluslabs.ai

Dispatching

When the user invokes /dcs-test without arguments, run:

go run ./apps/cloud/apps/dcs/src/tests/cmd/dcs-check unit

When a profile is specified, run exactly that profile through dcs-check, dcs-smoke, or dcs-gauntlet. Prefer go run ./apps/cloud/apps/dcs/src/tests/cmd/<tool> inside the repo unless the binary is already installed.

Remote Linux/KVM

For profiles that need Linux, /dev/kvm, or /dev/fuse, use the typed testbox CLI:

pnpm dcs testbox run "cargo build --release -p dm-host-agent -p dm-storage-daemon -p dm-bake -p dm-guest-agent"
pnpm dcs testbox run "sudo ./target/release/dm-check --iters 2"
pnpm dcs testbox run "go run ./apps/cloud/apps/dcs/src/tests/cmd/dcs-check kvm"

Read the full file on GitHub · 84 lines

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. 10d ago First seen · 84 lines · 41 tokens per session scan B b9bd9da730f8

Subscribe to this mod's changes

dcs-test is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (27 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 840 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

api-testing

Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.

cyanheads/obsidian-mcp-server · 46 tokens

add-test

Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.

cyanheads/obsidian-mcp-server · 41 tokens

email-formatting

Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.

provos/ironcurtain · 53 tokens

dogfood

This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.

AtlasOmnia/donna-starter · 20 tokens

holix-cron

Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts).

javded-itres/Holix · 25 tokens

blazemeter-api-reference

Comprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints. Use when working with BlazeMeter APIs for (1) Understanding BlazeMeter REST API structure, (2) Authenticating API requests, (3) Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.), (4) Using Test…

Blazemeter/bzm-mcp · 109 tokens