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-quality-reviewergit 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-quality-reviewer)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-quality-reviewer"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-quality-reviewer/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-quality-reviewer"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-quality-reviewer.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.00049 | $0.02641 |
| Opus 5.5 | $0.00020 | $0.01056 |
| Sonnet 5.5 | $0.00010 | $0.00528 |
| Haiku 4.5 | $0.00005 | $0.00264 |
Grade A, and why
frontend-quality-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Quality Reviewer
Purpose
Review frontend work for correctness, maintainability, decomposition, security, performance, TypeScript safety, architecture fit, visual quality, UX gates, verification honesty, and independent loop judgment without turning review findings into an unapproved rewrite.
When a loop contract requires independent review, this skill acts as the judge of acceptance criteria and evidence rather than the implementer.
When To Use
Use this skill when:
- the user asks for review, audit, critique, or quality check;
- a significant frontend implementation needs a final quality pass;
- a bugfix or refactor has broad impact and review is appropriate;
- a loop contract requires independent review;
- verification failed and was repaired during a loop;
- claims about security, performance, architecture, decomposition, visual fidelity, UX, or verification need evidence.
When Not To Use
Do not use this skill for direct implementation, bugfixing, refactoring, design spec writing, visual QA only, test creation, package installation, or broad rewrites.
If review finds required fixes, report them first. Do not apply fixes unless the user asked for a combined review-and-fix task or explicitly approves a follow-up fix.
Required Context
- Read
AGENTS.md. - Read
common/review-severity-model.md. - Read
common/independent-review-rules.mdwhen acting as loop judge or independent reviewer. - Read the current Goal Contract, Execution Plan, coverage map, and stable identifiers when the work uses durable planning.
- Read
common/verification-loop-rules.mdwhen loop attempts or verification evidence are in scope. - Read
common/approved-patterns.mdandcommon/anti-patterns.mdwhen reviewing changed components. - Read
common/ui-ux-priority-checklist.mdwhen reviewing rendered UI or user interaction. - Read conditional UX rules only when the changed surface includes them:
common/css-modules-specificity-rules.mdfor CSS Modules changes;common/form-feedback-rules.mdfor forms and feedback states;common/navigation-ux-rules.mdfor navigation and route flows;common/data-visualization-rules.mdfor dashboards, charts, tables, metrics, or reports;common/icon-quality-rules.mdfor icons or visual symbols;common/mobile-responsive-rules.mdfor responsive surfaces.
- Read
common/typescript-discipline.mdfor TypeScript surfaces. - Read
common/security-review-rules.mdwhen auth, secrets, unsafe HTML, redirects, external input, or permissions are in scope. - Read
common/performance-review-rules.mdwhen performance claims are in scope. - Read
common/build-tool-boundary-rules.mdandcommon/lint-verification-rules.mdwhen code changed. - Read affected source files, diffs, project overlays, loop contract, verification output, and rendered evidence needed for the review.
What ships with it
3 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.
- 1mo ago Changed · +10 lines 84a184653305
- 1mo ago Changed · +22 lines 12163ca6da8e
- 1mo ago First seen · 203 lines · 49 tokens per session scan A 2247daa764ea
frontend-quality-reviewer is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,641 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
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
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…
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…
code-reviewer
Use when asked to review, check or diagnose Spring Boot code: a pull request, diff, module or file before it merges; a slow endpoint or query (N+1, unbounded reads, JPA and Hibernate performance); security, JSpecify null-safety, architecture boundaries or Boot 4 migration risks in existing code; or whether the tests…
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…
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…