Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DKeken/codex-skills-alternativenpx agentmods add skills/dkeken/codex-skills-alternative/design-qaWrote 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/dkeken/codex-skills-alternative/design-qa)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/design-qa"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-qa/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/dkeken/codex-skills-alternative/design-qa"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-qa.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.00103 | $0.00919 |
| Opus 5 | $0.00051 | $0.00460 |
| Sonnet 5 | $0.00021 | $0.00184 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
design-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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — Design QA
Verify the built prototype actually matches the intended design + requirements. Catch drift before it ships. Unlike design-audit (open-ended critique of any UI), QA is a conformance check against a known source of truth — it answers "does this match what we agreed to build?"
When to use
- A prototype is built and you need to confirm it matches the mockup/spec before review.
- Final gate before
design-shareor dev handoff. - "Does it match the design?", "conformance check".
When NOT to use
- No spec/reference to compare against → that's open critique →
design-audit. - Nothing built yet → build it first.
Inputs
- The built prototype (local URL or path).
- The source of truth: reference image/mockup,
./design/context.md,./design/ideate/*. - Acceptance/success criteria (from context).
Workflow
- Capture the implementation via a browser-automation tool — screenshots of key screens and states (loading/empty/error/success).
- Visual conformance — compare to the reference: layout, type scale, spacing rhythm, palette, radii/shadows, iconography. Note every drift with the expected vs actual value.
- Behavioral conformance — walk the flow: do interactions, states, and navigation match the intended UX?
- Requirements conformance — does it satisfy the goal + success criteria from context? Any scope item missing?
- Accessibility sanity — contrast, focus order, target size, keyboard reachability (flag what needs manual AT testing — automated checks aren't full WCAG).
- Write
./design/qa.md: PASS items + prioritized fix list (severity × effort) + a verdict.
Output: ./design/qa.md
prototype: http://localhost:5173 source: ./mocks/onboarding.png + context.md
visual:
✓ layout matches ✗ body type 14px (spec 16px) ✗ accent #7C3 (spec #6366F1)
behavior:
✓ happy path ✗ no error state on empty name (spec requires inline error)
requirements (vs success criteria):
✓ 3-step wizard ✓ progress saved ✗ missing "skip" affordance (scope v1)
a11y:
✗ CTA contrast 3.1:1 (<4.5) manual: screen-reader pass still required
verdict: NOT READY — 4 fixes (2 HIGH: error state, contrast). Loop to design-prototype.
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.
- 9d ago First seen · 63 lines · 103 tokens per session scan A 2490e044d13d
design-qa is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 3mo ago), licensed MIT. It adds 103 tokens to every session and 919 once invoked, about $0.0005 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
create-workflow-diagram
Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions. Renders beautiful HTML diagrams with connected nodes, arrows, and labels, then screenshots them for sharing.
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
ui-designer/design-system
A shared set of rules for a product’s visual design, covering colors, fonts, spacing, corner shapes, shadows, and animations.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.