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 TheGoat395/Codex-Skills --skill frontend-quality-auditorgit clone --depth 1 https://github.com/TheGoat395/Codex-SkillsWrote 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/thegoat395/codex-skills/frontend-quality-auditor)<a href="https://agentmods.dev/skills/thegoat395/codex-skills/frontend-quality-auditor"><img src="https://agentmods.dev/badge/skills/thegoat395/codex-skills/frontend-quality-auditor/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/thegoat395/codex-skills/frontend-quality-auditor"><img src="https://agentmods.dev/badge/skills/thegoat395/codex-skills/frontend-quality-auditor.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.00016 | $0.00924 |
| Opus 5 | $0.00008 | $0.00462 |
| Sonnet 5 | $0.00003 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
frontend-quality-auditor 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 today.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Quality Auditor
Use this skill to decide whether a frontend is ready to ship and what should be fixed first.
Core Contract
Produce a concise, evidence-based quality report. Do not redesign the product unless the user explicitly asks for fixes. The default output is an audit, not a rebuild.
Audit Workflow
- Identify the project type, framework, entry routes, styling system, scripts, and available preview or deployment URL.
- Inspect source structure first, then inspect rendered output when a browser or screenshot workflow is available.
- Review desktop and mobile breakpoints before judging visual quality.
- Check the launch-critical surfaces: hero or first screen, navigation, primary CTA, forms, media, interactive states, footer, error/loading/empty states, and any checkout, booking, pricing, or dashboard flows.
- Classify issues by severity:
- Blocker: likely broken, inaccessible, misleading, unusable, or launch-damaging.
- High: visibly unprofessional, confusing, slow, fragile, or trust-reducing.
- Medium: polish, consistency, or resilience issue worth fixing soon.
- Low: minor refinement that should not block launch.
- Recommend the smallest useful next action for each meaningful issue.
- End with a clear Ship, Ship after fixes, or Do not ship yet judgment.
Review Areas
- Visual polish: hierarchy, spacing, typography, alignment, density, color, contrast, icon use, media treatment, empty space, and generic AI-looking patterns.
- Responsive behavior: mobile composition, tablet layout, overflow, touch targets, nav behavior, media crops, and text wrapping.
- Accessibility: semantic structure, headings, labels, focus states, keyboard paths, alt text, contrast, reduced motion, ARIA misuse, and modal/menu behavior.
- Performance: image and video weight, layout shift risk, font loading, animation cost, bundle hints, third-party scripts, and Core Web Vitals concerns.
- SEO and sharing basics: title, description, canonical, Open Graph, heading order, crawlable content, image alt text, sitemap/robots signals when relevant.
- Interaction quality: hover, focus, active, disabled, loading, error, success, offline, retry, and empty states.
- Content and trust: vague claims, placeholder copy, weak CTAs, unsupported proof, unclear pricing or contact flows, missing legal or support signals where expected.
What ships with it
2 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.
- today Changed 0616f5c19b5a
- 5d ago Changed · +4 lines · -59 tokens per session c3543c832493
- 11d ago First seen · 64 lines · 75 tokens per session scan A 439c56a65e7c
frontend-quality-auditor is a skill published in the GitHub repository TheGoat395/Codex-Skills (122 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 924 once invoked, about $0.0001 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-30.
Other skills, from other repositories
responsive-ui-qa
Inspect, diagnose, fix, and verify responsive frontend defects across routes, states, containers, and input modes. Use for mobile or desktop QA, overflow, overlap, broken navigation, unstable grids, clipped text, blank media, viewport regressions, screenshot comparison, and post-implementation visual verification.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.