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 ZachArticulateV/designer-pro-and-seo --skill qa-gategit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/qa-gate)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/qa-gate"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/qa-gate/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/zacharticulatev/designer-pro-and-seo/qa-gate"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/qa-gate.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.00139 | $0.01136 |
| Opus 5 | $0.00069 | $0.00568 |
| Sonnet 5 | $0.00028 | $0.00227 |
| Haiku 4.5 | $0.00014 | $0.00114 |
Grade A, and why
qa-gate 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 11d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qa-gate
Family: build-and-qa Status: Stable
Purpose
The mandatory pre-delivery gate for any client-bound build. Walks the build through 9 phases and produces a structured pass/fail report with a risk rating and an explicit YES/NO client-ready verdict. This is the gate, not the fix — it reports; remediation happens in the appropriate skills.
Triggers
- "qa check" / "qa gate"
- "is this ready to ship" / "client-ready check"
- "pre-delivery review"
- "stress test the site"
Inputs
- Build URL or local path
- Target client/audience
- Deployment target (Vercel, WordPress, GHL, etc.)
- Brief or original spec (for the completeness check)
Steps
- Load the report template
templates/qa-report-template.md. - Detect tooling. Check whether the Playwright extension is available
(see
extensions/playwright/). If yes, use it for live phases; if no, run the static path and mark live-only checksN/A — needs Playwright. - Run the 9 phases, recording PASS / WARN / FAIL / N/A for each:
- Functional — forms submit, links resolve, no console JS errors.
- Visual fidelity — matches the design system; responsive at 375/768/1280;
no broken layouts. (Playwright deepens this;
design-visual-qafor diffs.) - Accessibility — dispatch the
design-accessibilityagent (axe + WCAG AA when Playwright is connected; else its bundleda11y_static.pystructural checks — contrast, alt text, heading order, labels, focus visibility). - Performance — Core Web Vitals (LCP < 2.5s, CLS < 0.1, INP < 200ms).
Dispatch the
seo-googleagent for PSI/CrUX field data when a key/MCP is connected (the free PSI/CrUX key is preferred; any paid call routes throughcost_guard.py, which fails open to the free path); else flag CWV for field verification. - Security — HTTPS, security headers, no exposed secrets in source, audit third-party scripts.
- Content completeness — no lorem ipsum, no broken images, no placeholder copy; compare against the brief for missing pieces.
- SEO baseline — dispatch the
seo-pageagent (title, meta, OG, schema, canonical, images, internal links) as a real fan-out, not a prose handoff. - Cross-device / browser — sanity at key breakpoints/browsers.
- Deployment readiness — env vars set, redirects, analytics installed, DNS.
- Apply the verdict rule. Any unresolved CRITICAL ⇒ OVERALL = FAIL and CLIENT-READY = NO. CONDITIONAL PASS only when remaining items are WARN or lower.
- Estimate fix time and bucket findings into Critical / Warnings / Recommendations / Nice-to-haves.
- Render the filled
qa-report-template.md. Never declare client-ready with an open critical issue.
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.
- 11d ago First seen · 85 lines · 139 tokens per session scan A f22402b6f13d
qa-gate is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 139 tokens to every session and 1,136 once invoked, about $0.0007 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
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
schema-validator
Validate token files against DTCG 2025.10, Style Dictionary, or custom schemas. Trigger when someone says: validate token JSON, check my token files for errors, schema validation for tokens, are my token files valid, DTCG compliance check, validate token format, or anything about checking whether token files are…
visual-qa
Automated visual QA for a running frontend — screenshots the real rendered UI at the project's breakpoints and checks it against the project's own spec (tokens, layout rules, design language) AND its sibling screens, not hardcoded assumptions. Standalone on any frontend project; learns the project profile from docs/…
writing-skills
Use when creating a new forge-skill, editing an existing skill, when planning to contribute to forge-skills, when a session has produced a one-off prompt that should be promoted to a skill, or when verifying a skill works before deployment.
tdd
Use when implementing features or fixing bugs test-first, when user mentions "red-green-refactor", when test discipline is required for a specific task, when incremental-implementation needs TDD enforcement, or when a behavior change needs a failing test before any code is written.