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.
npx agentmods add skills/wolfenazz/yzpzcode/open-design-landingnpx skills add wolfenazz/YzPzCode --skill open-design-landinggit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/open-design-landing)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/open-design-landing"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/open-design-landing.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 | $0.00121 | $0.03300 |
| Opus 5 | $0.00060 | $0.01650 |
| Sonnet 5 | $0.00024 | $0.00660 |
| Haiku 4.5 | $0.00012 | $0.00330 |
Grade A, and why
open-design-landing 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 yesterday.
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.
This is a copy
94% identical to open-design-landing — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
open-design-landing
Build a single-page editorial landing site (or a slide deck — see the
sibling open-design-landing-deck skill)
in the Atelier Zero design system: warm-paper background, Inter
Tight + Playfair Display, italic serif emphasis spans, dotted hairline
rules, coral terminating dots, scroll-reveal motion, and 16 surreal
collage plates.
This is the canonical Open Design marketing-page recipe — the example output is the very page you see at open-design.
The skill is fully parameterized. The agent fills one typed
inputs.json from the user's brief; the composer turns that JSON +
the canonical styles.css into a deployable artifact.
inputs.json + styles.css 16 image slots
│ │
└──────────► scripts/compose.ts ◄────────────┘
│
▼
<out>/index.html (self-contained)
<out>/assets/ (PNG or SVG)
What you get
A single HTML file with all of:
- Editorial topbar (volume / issue / language strip), Headroom-style sticky nav with live GitHub star count.
- 8 numbered Roman-numeral sections with paper-textured background: hero (with 3 stat rings + 4-step index), about, capabilities (4 cards), labs (5 cards + filter pills + progress bar), method (4 steps with thumbnails), selected work (dark slab + 2 tilted cards), testimonial (pull quote + 5 partner glyphs), CTA (ribbon + email pill).
- Footer with 4 link columns + huge italic-serif kicker word.
- Scroll-reveal motion on every section (IntersectionObserver, respects
prefers-reduced-motion). - Fully responsive at 1280 / 1080 / 880 / 560 breakpoints.
Workflow contract
Run these four steps in order. The agent should complete each step before moving on, and prefer asking the user a focused question over inventing copy.
What ships with it
26 files 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.
- assets/about.png 1876 KB
- assets/capabilities.png 1846 KB
- assets/cta.png 1929 KB
- assets/hero.png 2011 KB
- assets/image-manifest.json 3.9 KB
- assets/imagegen-prompts.md 9.7 KB
- assets/lab-1.png 1269 KB
- assets/lab-2.png 1314 KB
- assets/lab-3.png 1291 KB
- assets/lab-4.png 1217 KB
- assets/lab-5.png 1143 KB
- assets/method-1.png 1082 KB
- assets/method-2.png 1115 KB
- assets/method-3.png 983 KB
- assets/method-4.png 994 KB
- assets/testimonial.png 1697 KB
- assets/work-1.png 1202 KB
- assets/work-2.png 1337 KB
- example.html 91 KB
- inputs.example.json 20 KB
- README.md 4.9 KB
- schema.ts 13 KB runs code
- scripts/compose.ts 29 KB runs code
- scripts/imagegen.ts 14 KB runs code
- scripts/placeholder.ts 7.6 KB runs code
- styles.css 46 KB
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.
- yesterday First seen · 321 lines · 121 tokens per session scan A d8c5d4559bee
open-design-landing is a skill published in the GitHub repository wolfenazz/YzPzCode (13 stars, last pushed today), licensed Apache-2.0. It adds 121 tokens to every session and 3,300 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to open-design-landing, differing in 51 lines, and is treated as a copy.
Other skills, from other repositories
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it…
omh-accessibility-audit
This is a Hermes-native accessibility-audit workflow skill.
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via…
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).