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 ytvee-dev/webdev-agent-kit --skill frontend-layout-implementergit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWrote 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/ytvee-dev/webdev-agent-kit/frontend-layout-implementer)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-layout-implementer"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-layout-implementer/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/ytvee-dev/webdev-agent-kit/frontend-layout-implementer"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-layout-implementer.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.00050 | $0.02526 |
| Opus 5.5 | $0.00020 | $0.01010 |
| Sonnet 5.5 | $0.00010 | $0.00505 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
frontend-layout-implementer 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 3d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Layout Implementer
Purpose
Implement a Design Implementation Spec or Design Direction Contract in a React or Next.js project while respecting existing CSS Modules, Redux, TanStack, Axios, architecture, styling, decomposition, UX gates, and verification conventions.
When the user asks to keep iterating until measurable visual, lint, build, or route acceptance criteria pass, implementation must follow a Loop Workflow Contract or hand off to loop-workflow-planner before editing.
When To Use
- The user asks to build a screen, section, component, or static page from a
Design Implementation Spec. - The user supplies screenshot-derived design material and asks for code in the current supported frontend project.
- The implementation target is within React, Next.js, CSS Modules, Redux, TanStack, or Axios scope.
When Not To Use
- The design intent has not been converted into a spec from supplied links or
screenshots. Use
design-screenshot-specfirst, then resume requested code work. - The user asks only for live design inspection, canvas edits, or whiteboard work.
- The project is outside the supported target stack unless the user explicitly changes scope.
- The task is unrelated to frontend rendering or layout.
Required Context
- Read
AGENTS.md. - Read
common/target-stack-policy.md. - Confirm the classified task is
frontend-layout,feature/development,bugfix,refactor, oroptimizationfor a rendered React or Next.js surface. - Read
common/approved-patterns.mdand relevant anti-pattern rules. - Read
common/css-modules-specificity-rules.mdfor CSS Modules changes. - Read conditional UX rules only when the touched surface needs them: forms, navigation, data visualization, icons, or mobile responsive behavior.
- Read
common/agent-loop-policy.mdandcommon/verification-loop-rules.mdwhen measurable iteration or bounded retry is required. - Read relevant project overlays when present: stack, architecture, styling, verification, state, data-fetching, build, and workspace profiles.
- Read the
Design Implementation Spec,Design Direction Contract, and supplied visual references. - Read affected source files, styles, components, routes, and configs.
- Read
references/implementation-rules.mdwhen present.
What ships with it
2 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.
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.
- 3d ago Changed · +6 lines dc21c4d9f4ee
- 1mo ago Changed · +30 lines · +1 tokens per session 4d8bd1b4b11a
- 1mo ago First seen · 173 lines · 49 tokens per session scan A 507c9643fcf5
frontend-layout-implementer is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,526 once invoked, about $0.0002 per session on Opus 5.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
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
playwright-frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React…
harness-design
Quality harness for design-dna Phase 3 output with browser-based visual verification. After an agent generates a design from a Design DNA JSON + user content, this skill acts as a verification and scoring layer — collecting all page resources via console/network inspection, performing section-by-section screenshot…
hmi-design-full
Comprehensive ISA-101 design rules for Human Machine Interfaces in process automation, with detailed reference files covering color design, display hierarchy, navigation, alarms, human factors, performance, and lifecycle management. Use when designing, building, reviewing, or generating code for HMIs, control system…
hmi-design-light
ISA-101 design rules for Human Machine Interfaces in process automation, covering display hierarchy, color standards, alarm integration, navigation, and situation awareness. Use when designing, building, reviewing, or generating code for HMIs, control system displays, SCADA screens, operator dashboards, or industrial…
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…