validate

A code-checking command that compares files with design tokens, craft principles, and design guidance stored in Subcog.

In plain words
What is it for?
Use it to validate code files against project-specific design rules.
Why use it?
It helps catch differences between the code and the project's intended visual or implementation rules. The input does not explain what Subcog is.

Command for Claude Code

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/zircote-plugins/aesth/validate
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/aesth

Made for: Claude Code.

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,139 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.00021 $0.01139
Opus 5 $0.00010 $0.00570
Sonnet 5 $0.00004 $0.00228
Haiku 4.5 $0.00002 $0.00114

Measured yesterday against content hash c5b60f763d6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

validate scanned grade B with 1 finding 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 yesterday.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat > ~/.claude/mnemonic/default/learnings/user/${UUID}-validation-insight.memory.md << 'MEMORY'
.claude/commands/validate.md · 171 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 171 lines · 21 tokens per session scan B c5b60f763d6e

Subscribe to this mod's changes

validate is a command published in the GitHub repository zircote-plugins/aesth (2 stars, last pushed 2mo ago), with no licence file. It adds 21 tokens to every session and 1,139 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.