harness:detect-design-drift

harness:detect-design-drift is a command for Claude Code from Intense-Visions/harness-engineering. It costs 46 tokens per session (318 once invoked), scanned A, original, MIT.

A read-only checker for finding design-system drift, meaning code that stops following the project's shared visual rules. It reports hardcoded values and raw HTML elements where defined design tokens or components should be used.

In plain words
What is it for?
It is for scanning candidate files against tokens and a component registry, reporting rule-based findings, and recording the results.
Why use it?
It makes inconsistencies visible without changing source files. Developers can then decide which findings need correction.

Command for Claude Code

Part of the harness-claude plugin — 85 skills, 89 commands, 17 agents, 4 hooks, 4 MCP servers shipped together

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/intense-visions/harness-engineering/detect-design-drift
Clone the repo
git clone --depth 1 https://github.com/Intense-Visions/harness-engineering

Made for: Claude Code.

Or install harness-claude, the plugin that ships this one along with the rest of its 85 skills, 89 commands, 17 agents, 4 hooks, 4 MCP servers.

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 harness:detect-design-drift

README.md
[![agentmods](https://agentmods.dev/badge/commands/intense-visions/harness-engineering/detect-design-drift.svg)](https://agentmods.dev/commands/intense-visions/harness-engineering/detect-design-drift)
Your own site
<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/detect-design-drift"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/detect-design-drift.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 318 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00318
Opus 5 $0.00023 $0.00159
Sonnet 5 $0.00009 $0.00064
Haiku 4.5 $0.00005 $0.00032

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

Security

Grade A, and why

harness:detect-design-drift 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 5d 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.

.claude-plugin/commands/detect-design-drift.md · 39 lines

What it actually says

Phases:

  • scan: Load tokens.json and DESIGN.md registry; walk candidate files
  • apply_rules: Run DRIFT-T* and DRIFT-P* rules per file
  • report: Aggregate severity, format findings, persist to graph

<execution_context> @agents/skills/claude-code/detect-design-drift/SKILL.md @agents/skills/claude-code/detect-design-drift/skill.yaml </execution_context>

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. 5d ago First seen · 39 lines · 46 tokens per session scan A 472a7f00e2d3

Subscribe to this mod's changes

harness:detect-design-drift is a command published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 318 once invoked, about $0.0002 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.