system-health

system-health is a command for Claude Code from murphytrueman/design-system-ops. It costs 7 tokens per session (232 once invoked), scanned A, original, MIT.

A command that assesses a design system, the shared rules and reusable components used to build a product’s interface. It scores seven areas, checks the system’s maturity, and produces a health report.

In plain words
What is it for?
Use it to review design tokens, components, documentation, adoption, governance, AI readiness, and platform support. It also creates findings and a prioritised action list.
Why use it?
It gives teams a structured view of what is working, what is weak, and what should be addressed first. Scores are adjusted to the system’s current maturity instead of using the same expectations for every team.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the design-system-ops plugin — 40 skills, 14 commands shipped together

Good fit Use it to review design tokens, components, documentation, adoption, governance, AI readiness, and platform support. It also creates findings and a prioritised action list.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add murphytrueman/design-system-ops
Claude Code
/plugin install design-system-ops

Made for: Claude Code.

Or install design-system-ops, the plugin that ships this one along with the rest of its 40 skills, 14 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.

agentmods badge for system-health

README.md
[![agentmods](https://agentmods.dev/badge/commands/murphytrueman/design-system-ops/system-health.svg)](https://agentmods.dev/commands/murphytrueman/design-system-ops/system-health)
Your own site
<a href="https://agentmods.dev/commands/murphytrueman/design-system-ops/system-health"><img src="https://agentmods.dev/badge/commands/murphytrueman/design-system-ops/system-health.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 232 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00007 $0.00232
Opus 5 $0.00003 $0.00116
Sonnet 5 $0.00001 $0.00046
Haiku 4.5 $0.00001 $0.00023

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

Security

Grade A, and why

system-health 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 8d 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.

commands/system-health.md · 17 lines

What it actually says

Run the system-health skill to produce a scored health assessment of the user's design system.

Load the system-health skill from ${CLAUDE_PLUGIN_ROOT}/skills/system-health/SKILL.md and follow its complete workflow.

Before starting, read the knowledge notes declared in the skill's frontmatter references: field, located in ${CLAUDE_PLUGIN_ROOT}/knowledge-notes/.

Begin with Step 1b (Baseline calibration) to establish the system's maturity level before scoring. Score all 7 dimensions (Tokens, Components, Documentation, Adoption, Governance, AI readiness, Platform maturity) with calibrated expectations appropriate to the system's maturity level.

Produce the full health report including: dimension scores out of 35, maturity level assessment, specific findings per dimension, and a prioritised action list.

If the user provides context about their system as an argument, use it: $ARGUMENTS

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. 8d ago First seen · 17 lines · 7 tokens per session scan A 232dca2318ff

Subscribe to this mod's changes

system-health is a command published in the GitHub repository murphytrueman/design-system-ops (176 stars, last pushed 16d ago), licensed MIT. It adds 7 tokens to every session and 232 once invoked, about $0.0000 per session on Opus 5. 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.