harness:design-pipeline

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

A command that runs several design-quality checks and optional fixes as one pipeline. It checks design drift, shared styling, component structure, brand rules, and visual polish.

In plain words
What is it for?
Use it to inspect or improve a project against its design documentation, design tokens, component patterns, and brand requirements.
Why use it?
It brings related design checks together and can repeat fixes until the reported problems converge.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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

Good fit Use it to inspect or improve a project against its design documentation, design tokens, component patterns, and brand requirements.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/intense-visions/harness-engineering/design-pipeline
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.

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, 16 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:design-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/commands/intense-visions/harness-engineering/design-pipeline.svg)](https://agentmods.dev/commands/intense-visions/harness-engineering/design-pipeline)
Your own site
<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/design-pipeline"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/design-pipeline.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 438 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.00062 $0.00438
Opus 5 $0.00031 $0.00219
Sonnet 5 $0.00012 $0.00088
Haiku 4.5 $0.00006 $0.00044

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

Security

Grade A, and why

harness:design-pipeline 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.

.claude-plugin/commands/design-pipeline.md · 44 lines

What it actually says

Phases:

  • freshen: Check input freshness (DESIGN.md, tokens.json, graph staleness) (optional)
  • detect: Invoke detect-design-drift; collect DRIFT-* findings
  • fix: Convergence loop with align-design-system (only when --fix is set) (optional)
  • audit: Generic Verifier registry loop (audit-anatomy + audit-brand)
  • fill: Bootstrap missing inputs + invoke design-craft POLISH (optional)
  • report: Compute verdict + summary

<execution_context> @agents/skills/claude-code/harness-design-pipeline/SKILL.md @agents/skills/claude-code/harness-design-pipeline/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. 8d ago First seen · 44 lines · 62 tokens per session scan A e9be6c680766

Subscribe to this mod's changes

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