qa-testing

qa-testing is a skill for Claude Code from rampstackco/claude-skills-starter. It costs 170 tokens per session (3,248 once invoked), scanned A, original, MIT.

A browser-based quality check for a web page, feature, or complete website, offered at smoke, standard, or full depth.

In plain words
What is it for?
Use it to check a deployment, investigate something that looks wrong, or verify a page, feature, or site before launch.
Why use it?
It helps find broken behavior and basic accessibility, performance, or search problems before or after a release.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rampstack-starter plugin — 14 skills shipped together

Good fit Use it to check a deployment, investigate something that looks wrong, or verify a page, feature, or site before launch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rampstackco/claude-skills-starter/qa-testing
Install

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.

Any agent
npx skills add rampstackco/claude-skills-starter --skill qa-testing
Clone the repo
git clone --depth 1 https://github.com/rampstackco/claude-skills-starter

Made for: Claude Code.

Or install rampstack-starter, the plugin that ships this one along with the rest of its 14 skills.

Wrote 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.

agentmods badge for qa-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/rampstackco/claude-skills-starter/qa-testing/github.svg)](https://agentmods.dev/skills/rampstackco/claude-skills-starter/qa-testing)
Your own site
<a href="https://agentmods.dev/skills/rampstackco/claude-skills-starter/qa-testing"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-starter/qa-testing/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.

agentmods 80×15 button for qa-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/rampstackco/claude-skills-starter/qa-testing"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-starter/qa-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 170 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,248 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00170 $0.03248
Opus 5.5 $0.00068 $0.01299
Sonnet 5.5 $0.00034 $0.00650
Haiku 4.5 $0.00017 $0.00325

Measured 17d ago against content hash 5984941bca7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qa-testing scanned grade A with 1 finding 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 17d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

fetch(window.location.origin, { method: 'HEAD' })
skills/qa-testing/SKILL.md · 303 lines

How it starts

The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Testing

Verify that a page, feature, or site is working before declaring it shipped. Stack-agnostic. Console-snippet driven for speed.

This skill is faster than accessibility-audit (which goes deeper on WCAG) and performance-optimization (which goes deeper on Core Web Vitals). Use this skill for general QA. Use the specialists for deep audits.


When to use

  • After every deploy (smoke test)
  • After launching a new page or feature (standard audit)
  • Before a major release (full release matrix)
  • Investigating a "something looks off" report
  • Pre-launch verification of a site or section

When NOT to use

  • Deep accessibility compliance work (use accessibility-audit)
  • Deep performance investigation (use performance-optimization)
  • Code review or debugging (use code-review-web)
  • Initial site setup or technical SEO baseline (use seo-technical)

Required inputs

  • The page URL or site under test
  • The tier of QA needed (smoke, standard, or full)
  • Browser dev tools access
  • Any specific concerns to check beyond the standard tier

The framework: 3 tiers

QA scales with the stakes. Pick the tier that matches the context.

Tier When to run Time Coverage
Smoke After every deploy 2 minutes Critical signals only
Standard New page or feature 10 minutes On-page basics, accessibility, structure
Full Major release, pre-launch 30+ minutes Comprehensive across all dimensions

Tier 1: Smoke test

The 2-minute "did the deploy break anything obvious?" check. Run after every deploy.

Console snippet (paste in browser dev tools):

const smoke = {
  title: document.title,
  titleLen: document.title.length,
  canonical: document.querySelector('link[rel="canonical"]')?.href,
  h1Count: document.querySelectorAll('h1').length,
  missingAlts: [...document.querySelectorAll('img')].filter(i => !i.hasAttribute('alt')).length,
  schema: [...document.querySelectorAll('script[type="application/ld+json"]')]
    .map(s => { try { return JSON.parse(s.innerText)['@type'] } catch(e) { return 'invalid' } }),
  brokenImages: [...document.querySelectorAll('img')].filter(i => !i.complete || i.naturalWidth === 0).length,
};
console.log(JSON.stringify(smoke, null, 2));

Read the full file on GitHub · 303 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 17d ago Changed · +8 lines · +47 tokens per session 5984941bca7a
  2. 1mo ago First seen · 295 lines · 123 tokens per session scan A 605f8489de7d

Subscribe to this mod's changes

qa-testing is a skill published in the GitHub repository rampstackco/claude-skills-starter (2 stars, last pushed 17d ago), licensed MIT. It adds 170 tokens to every session and 3,248 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

proof-e2e

Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".

tonone-ai/tonone · 63 tokens

playwright-expert

Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…

personamanagmentlayer/pcl · 77 tokens

selenium-expert

Expert in Selenium WebDriver, Selenium Grid, page object model, waits, cross-browser testing, and test automation frameworks. Use when the user mentions testing, end-to-end tests, QA, automation, WebDriver, or Selenium grid, or when the task involves Selenium Components, Browser Support, Advanced Features, or Basic…

personamanagmentlayer/pcl · 72 tokens

webqa

Use WebQA to test websites, web pages, URLs, login flows, search flows, forms, navigation, and core user journeys with an AI browser QA agent.

MigoXLab/webqa-agent · 36 tokens

e2e-testing

Playwright E2E testing patterns — Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies, PLUS the decision-time patterns that come before the first test is written (black-box helper scripts, static-vs-dynamic routing, multi-server orchestration, reconnaissance-then-action…

Nmor/the-claude-council · 70 tokens

dogfood

Exploratory QA of web apps: find bugs, evidence, reports.

NousResearch/hermes-agent · 18 tokens