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-bugfix-debuggergit 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-bugfix-debugger)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-bugfix-debugger"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-bugfix-debugger/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-bugfix-debugger"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-bugfix-debugger.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.01940 |
| Opus 5.5 | $0.00020 | $0.00776 |
| Sonnet 5.5 | $0.00010 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
frontend-bugfix-debugger 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Bugfix Debugger
Purpose
Fix frontend defects from symptoms and evidence while keeping the change small. When verification fails and repair is in scope, use a bounded retry loop instead of guessing repeatedly.
This skill must not turn a one-component presentation defect into a broad debugging, planning, visual QA, or full-repository verification workflow.
When To Use
Use this skill when the user asks to fix a frontend runtime, console, hydration, routing, rendering, interaction, styling, responsive, TypeScript, or build defect that needs evidence.
Use the Micro UI Fix Fast Lane from common/lightweight-routing-policy.md when the defect is an isolated presentation issue that stays within the micro UI hard limits.
When Not To Use
Do not use this skill for planned refactors, broad quality review, visual QA only, design intake, greenfield planning, backend-only debugging, package installation, or test creation.
If the task is a behavior-preserving refactor, use frontend-refactor-surgeon. If the user asks only for review, use frontend-quality-reviewer.
If the user only asks for options or an approach, answer with options first and do not edit files until implementation is requested or approved.
Required Context
- Read
AGENTS.md. - Read
common/prompt-intent-routing-rules.mdwhen workflow level is unclear. - Read
common/lightweight-routing-policy.mdfor micro UI fixes or other narrow code-changing tasks. - Read
common/debugging-evidence-rules.mdunless the defect is already explained by a narrow source inspection. - Read
common/agent-loop-policy.md,common/bounded-retry-rules.md, andcommon/verification-loop-rules.mdonly when the user asks to continue until verification passes, repeated failure appears, or bounded retry is needed. - Read
common/typescript-discipline.mdfor non-trivial TypeScript work. - Read relevant project overlays, especially
project/verification-profile.mdand path indexes, only when the task needs repository-specific verification commands or path facts. - Read the error, log, route, component, styles, or source files needed for the active bug hypothesis.
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.
- 1mo ago Changed 167275b7e43b
- 1mo ago First seen · 165 lines · 49 tokens per session scan A 7d33cb3e54f6
frontend-bugfix-debugger is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 7d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,940 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-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…
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…
technical-debt-audit
Use when the user says 'clean up my wordpress', 'what is bloating my wordpress', 'find orphaned shortcodes', or 'scan for unused plugins'. Audits orphaned shortcodes from deleted plugins, unused plugins, database bloat, unused media, and leftover data from inactive builders.
wordpress-site-dna
Use when the user says 'analyze my wordpress site', 'what is running on my site', 'site dna', or 'what plugins are on my site'. Detects every page builder, audits active versus dead-weight plugins, maps content structure, finds orphaned shortcodes, and checks performance and security posture.