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/ytvee-dev/webdev-agent-kit/frontend-layout-implementernpx skills add ytvee-dev/webdev-agent-kit --skill frontend-layout-implementergit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWhat 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.00049 | $0.02132 |
| Opus 5 | $0.00024 | $0.01066 |
| Sonnet 5 | $0.00010 | $0.00426 |
| Haiku 4.5 | $0.00005 | $0.00213 |
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 2d 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 — 173 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 and the source is only screenshots. Use
design-screenshot-specfirst. - The user asks for live Figma inspection, Figma MCP, canvas edits, or Figma whiteboard workflows.
- 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.
- 2d 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 (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,132 once invoked, about $0.0002 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
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-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
shipping-reproducible-results
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
actions-reusable-workflows
Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…
go-style
Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…
workflow-skill-evals
Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…