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-architecture-plannergit 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-architecture-planner)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-architecture-planner"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-architecture-planner/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-architecture-planner"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-architecture-planner.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.00047 | $0.01816 |
| Opus 5.5 | $0.00019 | $0.00726 |
| Sonnet 5.5 | $0.00009 | $0.00363 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
frontend-architecture-planner 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 14d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architecture Planner
Purpose
Plan frontend architecture decisions for React and Next.js projects when a task affects structure, ownership, routing, React state, Redux state, TanStack remote state, Axios data access, CSS Modules styling, form behavior, build/workspace shape, or long-lived conventions.
This skill creates an architecture decision and implementation handoff. It does not implement code by default.
When To Use
Use this skill after prompt intent routing when the task is Standard Workflow or Deep Workflow, the project is within the target stack, and architecture decisions matter.
Use this skill when the user asks to:
- plan a new React or Next.js feature that touches multiple modules;
- design a route, screen group, or application section;
- define component boundaries before implementation;
- decide where React, Redux, or TanStack state should live;
- decide how Axios or TanStack data fetching should fit the existing project;
- plan routing changes;
- plan form ownership and validation boundaries;
- plan a frontend refactor before editing code;
- assess architecture risk before implementation;
- define a greenfield React or Next.js architecture before scaffolding.
When Not To Use
Do not use this skill for:
- one small bug;
- one obvious type error;
- one small styling adjustment;
- one direct file-scope edit;
- unrelated frontend frameworks or app stacks;
- purely visual direction without architecture impact;
- rendered visual QA;
- UI component library selection;
- backend, database, ORM, migrations, or infrastructure work unless the user explicitly changes the scope.
Required Context
- Read
AGENTS.md. - Read
common/target-stack-policy.md. - Read
common/prompt-intent-routing-rules.mdwhen workflow level is unclear. - Read the compact goal contract or execution plan when present.
- Read only relevant boundary rules for the task.
- Read relevant project overlays when present: stack, architecture, styling, verification, docs, build, workspace, state, and data-fetching profiles.
- Read affected source files only when architectural boundaries cannot be planned from overlays.
- Do not read generated
dist/**during normal runtime.
What ships with it
1 file 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.
- 14d ago Changed · +6 lines c70138275fa3
- 1mo ago Changed · +7 lines 8f1c891cc66b
- 1mo ago First seen · 182 lines · 47 tokens per session scan A 6c5fe45418d1
frontend-architecture-planner 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 47 tokens to every session and 1,816 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
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…
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…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
frontend-dev-guidelines
Development guidelines for building front ends with Next.js 15, React 19, TypeScript, Shadcn/ui, and Tailwind CSS. They cover how pages, components, data fetching, routes, and project files should be organised.
coding-standards
React 19 and TypeScript coding standards for Portfolio Buddy 2. Use when: writing new components, reviewing code, refactoring, or ensuring consistency. Contains component patterns, TypeScript rules, and best practices.