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-linter-managernpx skills add ytvee-dev/webdev-agent-kit --skill frontend-linter-managergit 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.00037 | $0.01404 |
| Opus 5 | $0.00018 | $0.00702 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
frontend-linter-manager 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Linter Manager
Purpose
Run or plan lint verification for frontend code changes, repair related lint failures within a bounded loop, and manage user-requested lint setup safely.
When To Use
Use this skill after any code-changing fix, feature, refactor, implementation slice, or approved greenfield code creation.
Use it before code changes only when the user explicitly asks to add or repair lint setup.
When Not To Use
Do not use this skill for planning-only, design-only, documentation-only, README-only, or analysis-only tasks. Do not treat lint setup as a testing workflow.
Required Context
- Read
AGENTS.md. - Read package scripts or
project/verification-profile.mdto find existing lint commands. - Read
common/lint-verification-rules.mdandcommon/windows-shell-sandbox-rules.mdbefore rerunning a command that failed because of Windows shell policy or sandbox access. - Read
common/verification-loop-rules.mdandcommon/bounded-retry-rules.mdwhen lint repair is in scope. - Read only files needed to understand the package manager or workspace boundary.
Tool Contract
- May run an existing lint command after code changes.
- May inspect package scripts and workspace files.
- May use one equivalent
.cmdpackage-manager fallback on Windows after a PowerShell.ps1execution-policy block. - May update
project/verification-profile.mdwhen durable lint command facts are useful. - May fix lint failures related to the current change when safe and in scope.
- Must not add packages, scripts, or config files without explicit user approval.
- Must not change PowerShell execution policy.
- Must not repeat the same shell-blocked command after an equivalent fallback exists.
- Must not create tests or testing workflows.
- Must not introduce UI component libraries.
Workflow
- Detect the smallest relevant existing lint command.
- Run that command after the code change.
- If the command is blocked by Windows PowerShell
.ps1policy, retry once with the equivalent.cmdpackage-manager command when available. - If lint passes, record command and result.
- If lint fails, classify failures as related, likely pre-existing, unrelated environment issue, shell-blocked, sandbox-blocked, or unknown.
- If lint fails because of the current change, fix it when safe and in scope.
- Rerun the same lint command after related fixes.
- Use bounded retry rules when multiple related lint repair attempts are needed.
- Do not switch to an easier command just to claim success.
- Do not keep rerunning lint after the same shell or sandbox blocker repeats; report the blocker and verification impact.
- Report lint command, fallback command when used, result, attempt count, and unresolved lint issues.
- If no lint command exists, report that lint was not run.
- If the user asks for lint setup, propose a setup plan first and wait for approval.
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.
- 3d ago First seen · 142 lines · 37 tokens per session scan A e080bac909af
frontend-linter-manager 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 37 tokens to every session and 1,404 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…
diagnosing-ml-failures
Isolate the root cause of ML performance drops, inconsistent evaluations, prediction errors, and training-serving mismatches across data, labels, splits, pipelines, models, metrics, and runtime behavior. Use when investigating a reproducible failure or regression, not routine model selection or general performance…