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 LerianStudio/ring --skill checking-frontend-qualitygit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/checking-frontend-quality)<a href="https://agentmods.dev/skills/lerianstudio/ring/checking-frontend-quality"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/checking-frontend-quality/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/lerianstudio/ring/checking-frontend-quality"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/checking-frontend-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.00846 |
| Opus 5.5 | $0.00041 | $0.00338 |
| Sonnet 5.5 | $0.00020 | $0.00169 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
ring:checking-frontend-quality 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Quality Checks
When to use
- A frontend task needs standalone quality validation outside ring:running-dev-cycle-frontend (which owns these checks in Gate 0).
- You want to run one specific check (a11y, visual, e2e, or performance) against
changed UI components, or
allof them at once.
Skip when
- Backend-only project with no UI components.
- Task is documentation-only, configuration-only, or non-code.
- Changes limited to build tooling, CI/CD, or infrastructure.
- Inside ring:running-dev-cycle-frontend — that orchestrator already runs these in Gate 0.
Related
Complementary: ring:running-dev-cycle-frontend, ring:qa-frontend
Modes
| Mode | What it checks |
|---|---|
accessibility |
axe-core automated scans, zero WCAG 2.1 AA critical/serious violations, keyboard nav, focus management |
visual |
Snapshot tests across all component states and viewports (mobile 375px / tablet 768px / desktop 1280px) |
e2e |
Playwright user-flow tests across Chromium, Firefox, and WebKit (happy + error paths) |
performance |
Lighthouse > 90 and Core Web Vitals (LCP < 2.5s, CLS < 0.1, INP < 200ms), bundle budget |
all |
Runs all four modes in parallel and aggregates the verdicts |
The deep per-mode requirements live in the agent's mode files
(dev-team/agents/qa-frontend-modes/{accessibility,visual,e2e,performance}.md).
Do not duplicate them here.
Step 1: Validate Input
Required: unit_id (TASK id), implementation_files, gate0_handoffs.
Required: mode — one of accessibility | visual | e2e | performance | all.
Optional: components_list, user_flows_path, performance_baseline.
Step 2: Dispatch
For a single mode, dispatch the QA analyst with the selected mode:
Task:
subagent_type: "ring:qa-frontend"
description: "Frontend {mode} checks for {unit_id}"
prompt: |
mode: {mode}
unit_id: {unit_id}
implementation_files: {implementation_files filtered to UI files}
gate0_handoffs: {gate0_handoffs}
# optional, when relevant to the mode:
# user_flows_path, performance_baseline, components_list
Load qa-frontend-modes/{mode}.md and follow it.
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 First seen · 84 lines · 102 tokens per session scan A 32b9b941be02
ring:checking-frontend-quality is a skill published in the GitHub repository LerianStudio/ring (218 stars, last pushed 7d ago), licensed Apache-2.0. It adds 102 tokens to every session and 846 once invoked, about $0.0004 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-30.
Other skills, from other repositories
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…
chrome-cdp
Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…
code-audit
Batch audit of production files against CQ1-CQ40 quality gates and CAP1-CAP29 anti-patterns. Tiered output (A/B/C/D), critical gate enforcement, evidence-backed scoring, cross-file pattern analysis, and prioritized execution plan. Flags: zuvo:code-audit all | [path] | [file] | --deep | --quick | --services |…
pentest
Hybrid white-box + black-box penetration testing across 7 dimensions (PT1-PT7). Stack-aware source-to-sink tracing, exploit verification, CMS overlay, and deterministic finding aggregation. Uses explicit candidate schemas, canonical-key deduplication, score caps, and MUST-GATE enforcement. Flags: zuvo:pentest [path] |…