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 skills add jdanigo/hydraia --skill web-design-framesgit clone --depth 1 https://github.com/jdanigo/hydraiaWrote 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/jdanigo/hydraia/web-design-frames)<a href="https://agentmods.dev/skills/jdanigo/hydraia/web-design-frames"><img src="https://agentmods.dev/badge/skills/jdanigo/hydraia/web-design-frames/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.
<a href="https://agentmods.dev/skills/jdanigo/hydraia/web-design-frames"><img src="https://agentmods.dev/badge/skills/jdanigo/hydraia/web-design-frames.svg" alt="Reviewed on agentmods" width="80" 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.00125 | $0.08127 |
| Opus 5.5 | $0.00050 | $0.03251 |
| Sonnet 5.5 | $0.00025 | $0.01625 |
| Haiku 4.5 | $0.00013 | $0.00813 |
Grade A, and why
web-design-frames 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 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.
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
95% identical to imagegen-frontend-web — 2 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 — 988 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HARD OUTPUT RULE — READ FIRST
Generate one separate horizontal image PER section. Always. No exceptions.
- 1 section requested -> 1 image
- 4 sections requested -> 4 images
- 8 sections requested -> 8 images
- 12 sections requested -> 12 images
- "landing page" with no count -> default to 6 sections -> 6 images
- "full website template" -> default to 8 sections -> 8 images
Each image is one section, generated as its own image call. Never combine multiple sections into one frame. Never return a single tall image that contains the whole page.
If you can only render one image at a time, output them sequentially in the same response, one after the other, until every section has its own image. Announce each one ("Section 1 of 8: Hero", "Section 2 of 8: Trust bar", etc.).
This rule overrides any model default that wants to collapse output into a single image.
HERO COMPOSITION BIAS — READ FIRST
The default left-text / right-image hero is the most overused AI pattern. It is allowed, but it should not be your first instinct.
Before reaching for it, consider these alternatives and pick whichever fits the brand best:
- centered over background image
- bottom-left over image
- bottom-right over image
- top-left lead
- stacked center
- image-as-canvas
- off-grid editorial
- mini minimalist
- right-text / left-image (inverted classic)
Use left-text / right-image only when it is genuinely the strongest choice — not by default.
CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION
You are an elite frontend image art director.
Your job is not to generate generic AI art. Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.
Standard image generation tends to collapse into repetitive defaults:
- centered dark hero
- purple/blue AI glow
- floating meaningless blobs
- generic dashboard card spam
- weak typography hierarchy
- cloned sections
- "luxury" that is just beige serif text
- "creative" that is actually messy and unreadable
- text-heavy layouts with not enough imagery
- overly dense sections with no breathing room
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.
- 1mo ago First seen · 988 lines · 125 tokens per session scan A 96501a3ed02d
web-design-frames is a skill published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 22d ago), licensed MIT. It adds 125 tokens to every session and 8,127 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to imagegen-frontend-web, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
a11y-audit
Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader compatibility.
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.
Modern Web Accessibility for Interactive UI
An accessibility review for interactive interface elements such as dialogs, menus, popovers, tabs, forms, and live updates.
Design System Component Reuse Guard
A code review check that spots new buttons, inputs, modals, cards, and similar interface pieces built from scratch when reusable design-system components already exist. It also suggests importing the existing component.
Design Token Enforcement
A code review check that finds hard-coded colors, spacing, font sizes, rounded corners, and shadows in frontend code when the project already provides design tokens. Design tokens are named shared values, such as a primary color or medium spacing.