exec-check-requirement-audit

exec-check-requirement-audit is a skill for Claude Code, Codex from UCSC-VLAA/VisualClaw. It costs 33 tokens per session (229 once invoked), scanned A, original, MIT.

A checklist for reviewing a produced file against every requirement in the task.

In plain words
What is it for?
Use it for final audits of generated files when the task has explicit requirements such as required keys, assertions, citations, or minimum counts.
Why use it?
It helps catch missing fields, claims, citations, formats, or output paths before the work is considered finished.

Skill for Claude CodeCodex

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

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 skills/ucsc-vlaa/visualclaw/exec-check-requirement-audit
Any agent
npx skills add UCSC-VLAA/VisualClaw --skill exec-check-requirement-audit
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-requirement-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/ucsc-vlaa/visualclaw/exec-check-requirement-audit.svg)](https://agentmods.dev/skills/ucsc-vlaa/visualclaw/exec-check-requirement-audit)
Your own site
<a href="https://agentmods.dev/skills/ucsc-vlaa/visualclaw/exec-check-requirement-audit"><img src="https://agentmods.dev/badge/skills/ucsc-vlaa/visualclaw/exec-check-requirement-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 229 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00033 $0.00229
Opus 5 $0.00016 $0.00114
Sonnet 5 $0.00007 $0.00046
Haiku 4.5 $0.00003 $0.00023

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

Security

Grade A, and why

exec-check-requirement-audit 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 6d 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-requirement-audit/SKILL.md · 17 lines

What it actually says

Audit the Output Against Every Stated Requirement

  1. List the requirements: Re-read the task and extract every explicit requirement — required keys, required assertions, required citations, value formats, output path.
  2. Check each one: For every requirement, point to where the produced file satisfies it. If you cannot, the file is not done.
  3. Treat "must" / "include" / "at least N" as hard constraints: These are check-script conditions, not suggestions.
  4. Verify before declaring done: Do not end the round until every listed requirement is accounted for.

Example: Task says "list charge codes A, B, C and cite the clip" — confirm all three codes are present AND a clip citation exists before finishing.

Anti-pattern: Producing a plausible-looking file that silently omits one required field, assertion, or citation.

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. 6d ago First seen · 17 lines · 33 tokens per session scan A 3dc5fe71748e

Subscribe to this mod's changes

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