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/craft)<a href="https://agentmods.dev/skills/alanvaa06/award-craft/craft"><img src="https://agentmods.dev/badge/skills/alanvaa06/award-craft/craft.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.00084 | $0.01483 |
| Opus 5 | $0.00042 | $0.00741 |
| Sonnet 5 | $0.00017 | $0.00297 |
| Haiku 4.5 | $0.00008 | $0.00148 |
Grade A, and why
craft 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft — orchestrator
Run phases IN ORDER. One human gate. Never skip verify.
0. Preflight
Check and report before anything:
- CORE (stop with install instructions if missing): gsap-skills skills
available; impeccable v4+ available. Resolve its base dir once and reuse
it (later phases need its scripts) — first hit of
.agents/skills/impeccable,.claude/skills/impeccable,~/.claude/skills/impeccable. Readversion:from itsSKILL.mdfrontmatter: below 4.0 → stop and say so, because v4 changed the sharedDESIGN.mdcontract this plugin now writes against. Report the resolved path and version. - CORE for asset phase (continue but mark assets phase blocked): Higgsfield MCP tools reachable — also read the credit balance so the design plan's ceiling can be proposed against a real number.
- OPTIONAL (warn only): remotion/hyperframes skills (custom video — out of scope v0.1), ffmpeg on PATH (scroll-video frames) — becomes CORE if the approved design plan's signature moment uses scroll-video (re-check at the gate; block the build of that section and report if missing).
1. Intake
Inputs (any combination): text brief; @docs (PRD, brand doc, landing script
"guión" — script sections become the page structure); --brand <path> folder.
Brand source resolution, in order:
a) PRODUCT.md / DESIGN.md in the target repo → use them. They are SHARED with
impeccable (its init writes PRODUCT.md, its document/documenter writes
DESIGN.md). Read whatever is there and never clobber it: append the
award-craft sections that are missing, leave the rest alone. An
impeccable-written DESIGN.md is the incumbent visual world — direction
treats it as a brand source with drift rules, not as an empty slot.
b) External folder (--brand or ask) → IMPORT as local working copies with
provenance (source path + imported date). NEVER write to the business
folder — it is a source, not a destination.
c) Neither exists → create via interview.
ALWAYS ask comprehension questions (even with docs): offer, audience, primary
CTA, tone (3 adjectives), visual references/anti-references, which script
section is the climax (signature-moment candidate). One question at a time.
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.
- 7d ago First seen · 108 lines · 84 tokens per session scan A 196f4f74f012
craft is a skill published in the GitHub repository alanvaa06/award-craft (1 stars, last pushed 28d ago), licensed MIT. It adds 84 tokens to every session and 1,483 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…
kit-montar
Monta um site novo combinando peças já validadas do acervo pessoal do usuário — templates, design systems, componentes, animações, menus, prompts e receitas — em vez de gerar tudo do zero. Acervo vazio: constrói do zero e oferece guardar. Recebe o briefing, decide cor e tipografia antes da identidade, pergunta que…
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 コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.