A verification suite for checking whether configured integrations, skills, and commands are working and connected correctly.

It helps diagnose the environment after installation or configuration changes.

It distinguishes healthy, pending, failed, and skipped components and gives direction when setup or credentials are missing.

test — Command for coding agents by opensesh: A verification suite for checking whether configured integrations, skills…

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.

agentmods

npx agentmods add commands/opensesh/design-ops/test

Clone the repo

git clone --depth 1 https://github.com/opensesh/DESIGN-OPS

Or install design-ops, the plugin that ships this one along with the rest of its 5 skills, 13 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/opensesh/design-ops/test.svg)](https://agentmods.dev/commands/opensesh/design-ops/test)

Your own site

<a href="https://agentmods.dev/commands/opensesh/design-ops/test"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/test.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,846 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02846
Opus 5	$0.00000	$0.01423
Sonnet 5	$0.00000	$0.00569
Haiku 4.5	$0.00000	$0.00285

Measured 3d ago against content hash a3c7a2ba8cc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

test scanned grade B 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 3d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

3. MCP misconfigured — check ~/.claude/settings.json

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -H "Authorization: Bearer {token}" "https://api.figma.com/v1/me"

commands/test.md · 448 lines

How it starts

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

/design-ops:test

Verification suite that checks all integrations, skills, and commands are working correctly. Organized by pillars.

Also available as: /design-ops:doctor (alias for quick health check)

Trigger

User runs /design-ops:test to diagnose issues or verify setup after changes.

Connection Health Check

This test performs actual connection verification, not just config validation.

Health Status Definitions

Health	Meaning	Action
✓ Healthy	MCP responding, credentials valid, data accessible	None needed
⚠ Pending	Installed but needs OAuth/env setup to work	Follow fix guidance
✗ Error	Connection failed, check error details	Troubleshoot
○ Skipped	Not configured (optional)	Add via `/design-ops:configure`

Workflow

Step 1: Announce Test Suite

## DESIGN-OPS — Diagnostics

Running verification tests...

Step 2: Configuration Tests

### Configuration

Test 1: Config file exists

Check: ~/.claude/design-ops-config.yaml exists
Pass: [x] Config file exists
Fail: [ ] Config file not found — run /design-ops:setup

Test 2: Config syntax valid

Check: YAML parses without errors
Pass: [x] Config syntax valid
Fail: [ ] Config has syntax errors — see details below

Test 3: Config version

Check: version field is "2.0"
Pass: [x] Config version: 2.0
Warn: [~] Config version: 1.0 — run /design-ops:setup to migrate

Test 4: At least one pillar enabled

Check: At least one pillar has enabled: true
Pass: [x] Pillars enabled: {count}
Fail: [ ] No pillars enabled — run /design-ops:configure

Step 3: Operations Pillar Tests

### Operations Pillar

If pillar enabled:

For each tool in pillars.operations.tools:

Test: {Tool} connection

MCP: Try basic query
API: Validate token
Pass: [x] {Tool}: Connected
Fail: [ ] {Tool}: {error_message}

Read the full file on GitHub · 448 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.

3d ago First seen · 448 lines · 0 tokens per session scan B a3c7a2ba8cc0

Subscribe to this mod's changes

test is a command published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,846 tokens. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Testing claude-code claude-code-plugin design-tools figma github mcp

test