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 textura-agency/next16-claude-starter --skill qa-verifygit clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/qa-verify)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/qa-verify"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/qa-verify/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/textura-agency/next16-claude-starter/qa-verify"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/qa-verify.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.00099 | $0.01032 |
| Opus 5 | $0.00049 | $0.00516 |
| Sonnet 5 | $0.00020 | $0.00206 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
qa-verify 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA & verification
Two layers. The script decides what is decidable; you decide the rest. Never report "done" on the script alone — it cannot see a design.
Layer 1 — mechanical (always run first)
.claude/scripts/verify.sh # whole src/
.claude/scripts/verify.sh src/views/about.tsx # scoped
yarn lint
yarn build # must pass before anything ships
Every FAIL must be fixed. WARNs are judgement calls: fix or justify in your summary, do not silently ignore them.
Layer 2 — judgement checks
Work section by section. For each one:
Design fidelity (only when a design exists)
Re-fetch the Figma node — do not QA from memory or from your own earlier summary.
get_design_context for values, get_screenshot for layout. Then compare:
- Copy — character for character. Flag anything paraphrased, shortened or invented.
- Layout — column count, flex direction, alignment, order, positioning.
- Spacing — margins, padding, gaps against the design values.
- Typography — size, weight, line-height, letter-spacing. Never assume a heading is bold; designs often use 400.
- Colour — exact values, resolved through tokens rather than matched by eye.
- Images — aspect ratio, crop, radius, overlap. No effects the design lacks.
If an image looks invisible or wrong, check the container first — an invented wrapper background is the usual cause, not the asset itself.
Tokens
- Every colour/spacing/radius/type value resolves to a token.
- New tokens follow the three-tier grammar and carry a comment naming their origin.
- No literal reached
@theme inlineor a Tier 2 token. - A value that had to be invented because the design has no token for it is flagged to the user for design review, not quietly added.
Motion
- Everything scroll-driven, revealing, staggered or layout-affecting is a spring.
- CSS
transition-*appears only for hover/focus/discrete state, withduration-[var(--duration-*)]and a token ease. - Each primitive is the right one —
Inviewfor reveals,SpringTriggerscrub for parallax,Hoverfor hover, text through the text engine. tagis semantic on every animation component.- With
prefers-reduced-motion, content is present and readable.
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.
- 12d ago First seen · 95 lines · 99 tokens per session scan A 2d8689107285
qa-verify is a skill published in the GitHub repository textura-agency/next16-claude-starter (113 stars, last pushed 3d ago), licensed Unlicense. It adds 99 tokens to every session and 1,032 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
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
design-qa
Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…
health
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…
hunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…
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…
ui-craft-checks
Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…