harness:audit-component-anatomy

harness:audit-component-anatomy is a command for Claude Code from Intense-Visions/harness-engineering. It costs 55 tokens per session (336 once invoked), scanned A, original, MIT.

A command that checks UI component definitions for expected parts such as content areas, states, and sizes. It also looks for missing empty states for data and missing loading boundaries for asynchronous work.

In plain words
What is it for?
Use it to audit a component library, identify missing UI states, assign finding severity, and produce a report with component relationships.
Why use it?
It finds incomplete component designs before they cause confusing interfaces or unhandled loading and no-data situations.

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 audit a component library, identify missing UI states, assign finding severity, and produce a report with component relationships.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/intense-visions/harness-engineering/audit-component-anatomy
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:audit-component-anatomy

README.md
[![agentmods](https://agentmods.dev/badge/commands/intense-visions/harness-engineering/audit-component-anatomy.svg)](https://agentmods.dev/commands/intense-visions/harness-engineering/audit-component-anatomy)
Your own site
<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/audit-component-anatomy"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/audit-component-anatomy.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 336 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.00055 $0.00336
Opus 5 $0.00028 $0.00168
Sonnet 5 $0.00011 $0.00067
Haiku 4.5 $0.00006 $0.00034

Measured 7d ago against content hash 0fe28cf9d66c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

harness:audit-component-anatomy 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 7d 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/audit-component-anatomy.md · 41 lines

What it actually says

Phases:

  • scan: Identify component types and run convention/pattern audits
  • evaluate: Apply severity model based on design.strictness
  • report: Format findings as report + graph edges

<execution_context> @agents/skills/claude-code/audit-component-anatomy/SKILL.md @agents/skills/claude-code/audit-component-anatomy/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. 7d ago First seen · 41 lines · 55 tokens per session scan A 0fe28cf9d66c

Subscribe to this mod's changes

harness:audit-component-anatomy is a command published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 336 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.