exec-check-schema-fidelity

exec-check-schema-fidelity is a skill for Claude Code, Codex from UCSC-VLAA/VisualClaw. It costs 40 tokens per session (215 once invoked), scanned A, original, MIT.

A rule for matching an output exactly to a required data structure or file format.

In plain words
What is it for?
Use it when a task specifies exact keys, value formats, or an output path for a file.
Why use it?
It prevents schema checks from failing because of renamed, missing, extra, or incorrectly formatted fields.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a task specifies exact keys, value formats, or an output path for a file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ucsc-vlaa/visualclaw/exec-check-schema-fidelity
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 UCSC-VLAA/VisualClaw --skill exec-check-schema-fidelity
Clone the repo
git clone --depth 1 https://github.com/UCSC-VLAA/VisualClaw

Made for: Claude Code, Codex.

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 exec-check-schema-fidelity

README.md
[![agentmods](https://agentmods.dev/badge/skills/ucsc-vlaa/visualclaw/exec-check-schema-fidelity.svg)](https://agentmods.dev/skills/ucsc-vlaa/visualclaw/exec-check-schema-fidelity)
Your own site
<a href="https://agentmods.dev/skills/ucsc-vlaa/visualclaw/exec-check-schema-fidelity"><img src="https://agentmods.dev/badge/skills/ucsc-vlaa/visualclaw/exec-check-schema-fidelity.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 215 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.00040 $0.00215
Opus 5 $0.00020 $0.00108
Sonnet 5 $0.00008 $0.00043
Haiku 4.5 $0.00004 $0.00021

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

Security

Grade A, and why

exec-check-schema-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 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.

visualclaw/skills_seed/seed_visualclawarena/exec-check-schema-fidelity/SKILL.md · 17 lines

What it actually says

Match the Specified Schema Exactly

  1. Find the schema: The task, or a referenced schema file, defines the exact structure. Read it before writing.
  2. Use exact key names: Do not rename, pluralize, or invent fields. Missing or extra keys fail schema checks.
  3. Match value formats: Honor stated formats — currency strings, date formats, enumerated statuses, units.
  4. Write to the exact path: Produce the file at the path the task names, and only that file.

Example: A schema listing {item, sellable_count, damaged_count} requires those exact keys — not {name, count}.

Anti-pattern: Producing a well-intentioned file with differently-named fields the checker does not recognize.

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 · 17 lines · 40 tokens per session scan A f571b0c2765f

Subscribe to this mod's changes

exec-check-schema-fidelity is a skill published in the GitHub repository UCSC-VLAA/VisualClaw (55 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 215 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.