Borrowing it
Nothing to install: this file belongs to YankielDBC2/codex-skills-library. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/YankielDBC2/codex-skills-library/main/.agents/skills/pixel-perfect-qa/SKILL.mdgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/pixel-perfect-qa)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/pixel-perfect-qa"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/pixel-perfect-qa.svg" alt="Measured on agentmods" 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.00035 | $0.00383 |
| Opus 5 | $0.00017 | $0.00192 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
pixel-perfect-qa 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 6d 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.
What it actually says
Pixel Perfect QA
Goal
Catch visual, responsive, spacing, typography, alignment, and interaction issues before declaring UI work complete.
When to use
Use at the end of UI work, before handoff, before launch, after a redesign, or when the user asks if the page looks polished/professional.
Workflow
- Review layout alignment, spacing rhythm, type scale, hierarchy, color contrast, image crops, icon alignment, and responsive breakpoints.
- Check that mobile, tablet, and desktop each have intentional density and no accidental overflow.
- Inspect interactive states: hover, focus, active, disabled, loading, empty, error, and success when relevant.
- Check animation timing, cleanup, reduced-motion behavior, and whether motion supports the experience.
- Look for generic AI leftovers: placeholder copy, repeated cards, random gradients, oversized headings, or unused decorative elements.
- Fix small issues directly when safe; report larger issues separately if they require design decisions.
Quality bar
- Run build/lint/typecheck or the nearest project validation.
- Manually inspect critical breakpoints when possible.
- Confirm no console errors or layout overflow if browser validation is available.
Validation
- The page looks intentional at common breakpoints.
- Visual details align consistently and no obvious generic patterns remain.
- Interactive and responsive states are not ignored.
Final response
- Report QA findings fixed, remaining issues, and validation performed.
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.
- 6d ago First seen · 50 lines · 35 tokens per session scan A 6bafb207e0d4
pixel-perfect-qa is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 383 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
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
designer-skill
Use for UI design, implementation, redesign, visual review, accessibility, responsive behavior, interaction states, and design systems. Preserve established product identity unless the user authorizes a change. Do not activate for backend-only, database-only, CLI, or non-visual tasks. Reviews are read-only unless…
responsive-design
Use when mobile-first responsive design — breakpoints, fluid typography, container queries, and touch optimization. Use when working with responsive design.
interaction-physics
Design and implement the motion layer of a UI — microinteractions, transitions, hover/press feedback, and animation timing/easing — as working CSS/JS plus a written animation spec. Use when the user says 'the app feels janky', 'animations feel off', 'make it feel smoother/snappier', 'add a transition', 'the modal just…
Responsive Layout Reviewer
Reviews HTML/CSS or component code for responsive design issues across mobile, tablet, and desktop breakpoints.
design-foundation
Create or extract a design-token foundation — colors, typography, spacing, radii, shadows — as a real tokens file (CSS variables and/or Tailwind theme) plus a migration map from current hardcoded values. Use when the user says 'set up a design system', 'our styles are inconsistent', 'we have 50 shades of the same…