aidemo: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from tandryukha/aidemo. It costs 164 tokens per session (1,026 once invoked), scanned A, original, MIT.

A repeatable end-to-end check for an aidemo engine change, rendering a bundled example into a video and checking the output files.

In plain words
What is it for?
Use it after engine changes or when asked to verify that the example still renders, with either a real or local mock AI service.
Why use it?
It catches failures across the full rendering process instead of checking only one code component.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions AGENTS.md.

This is tandryukha/aidemo's own configuration. It tells Claude Code how to work on aidemo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aidemo configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node bin/aidemo.mjs render examples/local-demo --headless.

Reuse

Borrowing it

Nothing to install: this file belongs to tandryukha/aidemo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tandryukha/aidemo/main/.claude/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tandryukha/aidemo

Made for: Claude Code.

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 verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/tandryukha/aidemo/verify/github.svg)](https://agentmods.dev/skills/tandryukha/aidemo/verify)
Your own site
<a href="https://agentmods.dev/skills/tandryukha/aidemo/verify"><img src="https://agentmods.dev/badge/skills/tandryukha/aidemo/verify/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 verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/tandryukha/aidemo/verify"><img src="https://agentmods.dev/badge/skills/tandryukha/aidemo/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 164 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00164 $0.01026
Opus 5.5 $0.00066 $0.00410
Sonnet 5.5 $0.00033 $0.00205
Haiku 4.5 $0.00016 $0.00103

Measured 1mo ago against content hash 1d5903c87700, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify scanned grade A 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf http://localhost:8787 >/dev/null && echo up
.claude/skills/verify/SKILL.md · 92 lines

How it starts

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

verify — e2e smoke test for engine changes

Your job: prove a change to the engine still renders the self-contained fixture end-to-end. Be terse; surface only failures + a final status.

Phases

  1. Typecheck (always):

    npm run typecheck
    
  2. Fixture server (background; it's a plain static server on :8787):

    node examples/local-demo/serve.mjs &
    curl -sf http://localhost:8787 >/dev/null && echo up
    
  3. Full e2e (needs OPENAI_API_KEY in .env, or OPENAI_BASE_URL pointing at a local OpenAI-compatible server — check with node bin/aidemo.mjs doctor first; it reports the resolved endpoint):

    node bin/aidemo.mjs render examples/local-demo --headless
    

    If neither is available, prefer the offline full e2e — the bundled mock serves both endpoints locally, so every stage still runs, with zero API spend (say which path you used in the report):

    node test/mock-openai.mjs &            # mock TTS+STT on :8790
    OPENAI_API_KEY= OPENAI_BASE_URL=http://127.0.0.1:8790/v1 \
      node bin/aidemo.mjs render examples/local-demo --headless
    

    (Narration is sine tones and captions are placeholder words — fine for verifying the pipeline, useless for judging output quality.) Last resort: probe (selectors) + record + compose against previously generated audio//generated/ artifacts if present (captions --offline can regenerate caption cues from an existing voice.json without network).

  4. Inspect the output — existence is not enough:

    ffprobe -v error -show_entries format=duration -show_entries stream=codec_type \
      -of default=nw=1 examples/local-demo/output/final-demo.mp4
    

    Expect one video + one audio stream and a plausible duration (the fixture is ~30–60 s). A suspiciously tiny file or missing audio stream is a failure.

  5. Stage-scoped iteration — if the change touches one stage, re-run just it (voice, record, captions, compose, or probe for selector work) instead of a full re-render; each stage is independently re-runnable.

Read the full file on GitHub · 92 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. 1mo ago Changed · +2 lines 1d5903c87700
  2. 1mo ago First seen · 90 lines · 164 tokens per session scan A f2ecc3bbeaa6

Subscribe to this mod's changes

verify is a skill published in the GitHub repository tandryukha/aidemo (20 stars, last pushed 7d ago), licensed MIT. It adds 164 tokens to every session and 1,026 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

microsoft/playwright · 19 tokens

playwright-component-testing

Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.

microsoft/playwright · 69 tokens

playwright-trace

Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.

microsoft/playwright · 29 tokens

compatibility-testing

Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.

proffesor-for-testing/agentic-qe · 36 tokens

e2e-testing

Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…

ericrisco/rsc-harness · 79 tokens

Axe-core Accessibility Testing

Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.

PramodDutta/qaskills · 33 tokens