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 HermeticOrmus/design-mastery-claude-code --skill verify-design-masterygit clone --depth 1 https://github.com/HermeticOrmus/design-mastery-claude-codeWrote 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/hermeticormus/design-mastery-claude-code/verify-design-mastery)<a href="https://agentmods.dev/skills/hermeticormus/design-mastery-claude-code/verify-design-mastery"><img src="https://agentmods.dev/badge/skills/hermeticormus/design-mastery-claude-code/verify-design-mastery/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/hermeticormus/design-mastery-claude-code/verify-design-mastery"><img src="https://agentmods.dev/badge/skills/hermeticormus/design-mastery-claude-code/verify-design-mastery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00088 | $0.01487 |
| Opus 5.5 | $0.00035 | $0.00595 |
| Sonnet 5.5 | $0.00018 | $0.00297 |
| Haiku 4.5 | $0.00009 | $0.00149 |
Grade A, and why
verify-design-mastery 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 11d 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.
This is a copy
88% identical to verify-libreuiux — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify design-mastery-claude-code
design-mastery-claude-code is a plugin library, not a running app: a single plugin, installed from the repo root, published as the design-mastery marketplace. Its user surface is the install. A user adds this repo as a plugin marketplace in Claude Code or Grok Build, installs plugins from it (or runs ./setup.sh from a clone), and then uses the skills, commands, agents and hooks those plugins bring. This skill drives that path in throwaway configs, so a proof never touches your own Claude Code config or Grok home.
Helper (executable, bash; needs claude, grok, jq and git): .grok/skills/verify-design-mastery/bin/control-design-mastery
B=.grok/skills/verify-design-mastery/bin/control-design-mastery
$B --help
$B doctor # worth driving? CLIs, head, manifests in sync
$B run # every plugin, both CLIs, prove each loaded; one JSON result
$B run --only design-mastery # the same for the plugins a change touched
$B run --pr 12 --expect <sha> # the same on a PR head, fetched into a scratch clone
$B install --claude --only design-mastery # a fresh run that keeps its clean config for the next steps
$B details design-mastery # component inventory in the latest run (both CLIs)
$B setup --list # ./setup.sh inside the latest run's clean configs
$B check # scripts/check.sh, the repo's one check command
$B cleanup # drop every run's scratch; the evidence stays
JSON on stdout, progress on stderr, exit 1 on any failed proof. Everything the helper writes lives under VERIFY_DESIGN_MASTERY_HOME (default ~/.local/share/verify-design-mastery): runs/<stamp>-<head8>/ (or <stamp>-pr<N>-<head8>) holds scratch/ and evidence/, and runs/latest points at the newest run.
Launch
- There is no server. Launching is starting a run: a run folder with an empty Claude Code config (
CLAUDE_CONFIG_DIR) and an empty Grok home (GROK_HOME), both underscratch/. - The tree under test is the checkout the helper sits in. With
--pr Nit is a scratch clone ofrefs/pull/N/headfetched fromorigin, and--expect <sha>refuses any other head. - Claude Code adds the tree as the
design-masterymarketplace and installs<plugin>@design-mastery. Grok installs the repo root as one plugin:grok plugin install <checkout> --trust. - Ready when the marketplace add exits 0:
evidence/claude-marketplace-add.logandevidence/grok-marketplace-add.log(orgrok-install.log) end inexit 0. - Teardown:
runremoves its own scratch when it finishes. Afterinstall, runcleanupwhen you are done withdetailsandsetup.
What ships with it
6 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.
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.
- 11d ago First seen · 76 lines · 88 tokens per session scan A 74023585b480
verify-design-mastery is a skill published in the GitHub repository HermeticOrmus/design-mastery-claude-code (18 stars, last pushed 11d ago), licensed MIT. It adds 88 tokens to every session and 1,487 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to verify-libreuiux, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
figma-scan-code-accessibility
Scan generated/authored HTML for accessibility violations with axe-core (Deque) running over JSDOM — structural and semantic rules: ARIA attributes and roles, accessible names, alt text, form labels, heading order, landmarks, semantic HTML, tabindex, duplicate IDs, lang attribute, and 50 more. Use on the CODE side of…
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".