Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alanvaa06/award-craft/plugin install award-craftWrote 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.
[](https://agentmods.dev/skills/alanvaa06/award-craft/verify)<a href="https://agentmods.dev/skills/alanvaa06/award-craft/verify"><img src="https://agentmods.dev/badge/skills/alanvaa06/award-craft/verify.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.00582 |
| Opus 5 | $0.00036 | $0.00291 |
| Sonnet 5 | $0.00015 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
verify 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify — the loop that makes doctrine real
"Build succeeded" ≠ done. Done = rendered, screenshotted, critiqued, passing.
Protocol
- Ensure production build passes (
npm run build) — fix before any screenshots. - Start the dev server; open the page in the available browser tooling.
- Screenshot set: desktop 1280px AND mobile 375px, at minimum: top of page, each script section, the signature moment mid-animation, the footer. Mobile is evaluated as ITS OWN designed choreography, not shrunk desktop.
- Critique each screenshot against
${CLAUDE_PLUGIN_ROOT}/skills/verify/references/checklist.md — enumerate
concrete deltas, no vibes. Code checks (grep items) run once per pass.
Run impeccable's detector once per pass over the changed targets —
node <impeccable-base>/scripts/detect.mjs --json <targets>, base dir resolved in preflight — and fold its findings into the same list (checks 26-27). It catches the mechanical tells this checklist deliberately does not duplicate; do not eyeball them, and do not run it twice in one pass. When a comp was approved (docs/comps/), the critique is a SIDE-BY-SIDE: view the comp region and the built region together, the hero and each section as its own crop at legible scale — never one full-page thumbnail, which hides crude controls, wrong lettering character and flattened material behind a similar section order (checks 24-25). - Fix findings. Re-shoot affected screenshots.
- A screenshot that passes is renamed with the
verified_prefix. Loop until the whole set carries the prefix, then run ONE final confirmation pass. - Max 3 iterations per issue. Non-converging issues go to the report as pending — never loop infinitely, never silently drop.
- Output: verify report — checks passed/failed, pending issues, screenshot inventory, score against the Awwwards anatomy checklist (${CLAUDE_PLUGIN_ROOT}/skills/direction/references/awwwards-rubric.md).
Reduced-motion pass (mandatory)
Emulate prefers-reduced-motion; screenshot the same set. Full content must be visible and usable with no pin, no scrub, no parallax.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 41 lines · 73 tokens per session scan A 6360944666ad
verify is a skill published in the GitHub repository alanvaa06/award-craft (1 stars, last pushed 27d ago), licensed MIT. It adds 73 tokens to every session and 582 once invoked, about $0.0004 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.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
Component Variants / States Documentation コンポーネント状態の文書化
新規追加された UI コンポーネントに、variants（種類）とインタラクティブ状態（hover / focus / disabled / loading / error）が定義・文書化されているかを確認し、状態設計の欠落を検出する.
Design Source-of-Truth Conformance デザイン定義準拠
リポジトリに DESIGN.md やデザイントークン定義が存在する場合に、新規 UI 実装の色・余白・フォントサイズ・角丸・シャドウがその定義済みスケールに準拠しているかを照合する。定義が無ければ実行しない.
stark
Use for UI/UX design, product flows, frontend or native interface design, design audits, design translation, asset planning, motion direction, design tokens, or distinctive non-generic apps and websites. Covers web and React, Windows and WinUI/Mica, Apple and SwiftUI, Android and Jetpack Compose/Material…