agentmods.dev

validate-fidelity

validate-fidelity is a skill for Claude Code from big-emotion/agent-atelier. It costs 41 tokens per session (2,625 once invoked), scanned A, original, MIT.

A checking tool for comparing a written interface specification and a working website with reference data and screenshots of the original interface.

In plain words
What is it for?
Use it to check specifications, visual details, or both. You can check a whole website or focus on one component, such as a sidebar.
Why use it?
It finds differences between the planned, original, and built interface before those differences reach users.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the frontend-fidelity plugin — 3 skills shipped together

not rated 2repo 3d ago A scan 41 tokens original MIT

Good fit Use it to check specifications, visual details, or both. You can check a whole website or focus on one component, such as a sidebar.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/big-emotion/agent-atelier/validate-fidelity
View source ↗ big-emotion/agent-atelier
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.

Any agent
npx skills add big-emotion/agent-atelier --skill validate-fidelity
Clone the repo
git clone --depth 1 https://github.com/big-emotion/agent-atelier

Made for: Claude Code.

Or install frontend-fidelity, the plugin that ships this one along with the rest of its 3 skills.

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 validate-fidelity

README.md
[![agentmods](https://agentmods.dev/badge/skills/big-emotion/agent-atelier/validate-fidelity/github.svg)](https://agentmods.dev/skills/big-emotion/agent-atelier/validate-fidelity)
Your own site
<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/validate-fidelity"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/validate-fidelity/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.

agentmods 80×15 button for validate-fidelity

Your own site · 80×15
<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/validate-fidelity"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/validate-fidelity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,625 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.00041 $0.02625
Opus 5 $0.00020 $0.01313
Sonnet 5 $0.00008 $0.00525
Haiku 4.5 $0.00004 $0.00263

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

Security

Grade A, and why

validate-fidelity 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 10d 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.

plugins/frontend-fidelity/skills/validate-fidelity/SKILL.md · 257 lines

How it starts

The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Validate Fidelity — Spec & Visual Drift Detection

Compare specs and running implementations against the reverse-UI oracle to catch drift before it ships.

Input: $ARGUMENTS = --phase <spec|visual|all> [--domain <NNN-name>] [--focus <component>] [--oracle <path>]

Arguments

  • --phase (required): spec | visual | all
    • spec — validate spec document against oracle JSON data
    • visual — validate running app against oracle screenshots + structure
    • all — run both phases sequentially for all matching domains
  • --domain (optional): spec number or name, e.g., 004-home, 002-app-shell. If omitted, validates all domains that have both a spec and an oracle source.
  • --focus (optional): component name to narrow scope, e.g., sidebar, module-card. Only validates requirements related to this component.
  • --oracle (optional): path to reverse-UI output directory. Auto-detected if omitted.

Examples

/validate-fidelity --phase spec --domain 004-home
/validate-fidelity --phase visual --domain 004-home
/validate-fidelity --phase all
/validate-fidelity --phase spec --domain 002-app-shell --focus sidebar
/validate-fidelity --phase spec --oracle ./reverse-ui-localhost-3000

Phase 0: Parse Input & Locate Oracle

  1. Parse $ARGUMENTS for --phase, --domain, --focus, --oracle.
  2. If --phase is missing, ask the user which phase to run.
  3. Locate the oracle in this priority order: a. --oracle flag (explicit path) b. specs/assets/manifest.json → read meta.baseUrl to derive reverse-ui-{domain}/ c. Glob for reverse-ui-*/manifest.json in current working directory d. Ask user if not found
  4. Verify the oracle directory exists and contains manifest.json.
  5. If --domain is specified, locate the corresponding spec file: specs/{domain}.md
  6. If --domain is omitted, glob for all specs/*.md files and match each to an oracle page directory.
  7. Check for component-kit availability: component-kit-{domain}/manifest.json — if present, use it for more precise validation.

Read the full file on GitHub · 257 lines

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. 10d ago First seen · 257 lines · 41 tokens per session scan A e14716102d44

Subscribe to this mod's changes

validate-fidelity is a skill published in the GitHub repository big-emotion/agent-atelier (2 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 2,625 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-31.

CI and CDClaude CodeDesign and UXTestingatlassianclaude-code-pluginconventional-commitsdeveloper-tooling
Related

Other skills, from other repositories

cloudflare-workers-testing

Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.

secondsky/claude-skills · 57 tokens

accessibility-per-component

Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…

murphytrueman/design-system-ops · 65 tokens

cicd-integration

Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…

murphytrueman/design-system-ops · 177 tokens

schema-validator

Validate token files against DTCG 2025.10, Style Dictionary, or custom schemas. Trigger when someone says: validate token JSON, check my token files for errors, schema validation for tokens, are my token files valid, DTCG compliance check, validate token format, or anything about checking whether token files are…

murphytrueman/design-system-ops · 76 tokens

gitlab:ci-monitor

Watch GitLab CI and investigate pipeline failures. Use when a pipeline or job is failing or red, when watching MR CI, branch builds, or a specific pipeline, when waiting for CI to go green, or when authoring or validating .gitlab-ci.yml.

bendrucker/claude · 59 tokens

design

Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…

greglas75/zuvo · 90 tokens