qa-testing

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

A guide to checking whether a page, feature, or website works before it is considered shipped. It defines smoke tests, standard checks, and full regression testing, where existing functionality is checked after changes.

In plain words
What is it for?
Use it after deployments, before launches, when investigating reports that something looks wrong, and during release-wide checks.
Why use it?
It helps catch broken interactions, errors, and deployment problems before users find them. The testing depth can match the importance of the release.

Skill for Claude Code

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

Part of the rampstack-skills plugin — 103 skills shipped together

Good fit Use it after deployments, before launches, when investigating reports that something looks…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rampstackco/claude-skills/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 --skill qa-testing
Clone the repo
git clone --depth 1 https://github.com/rampstackco/claude-skills

Made for: Claude Code.

Or install rampstack-skills, the plugin that ships this one along with the rest of its 103 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/qa-testing.svg)](https://agentmods.dev/skills/rampstackco/claude-skills/qa-testing)
Your own site
<a href="https://agentmods.dev/skills/rampstackco/claude-skills/qa-testing"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/qa-testing.svg" alt="Measured on agentmods" 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 $0.00085 $0.01624
Sonnet 5 $0.00034 $0.00650
Haiku 4.5 $0.00017 $0.00325

Measured 3d ago against content hash 5984941bca7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 3d 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. 3d ago First seen · 303 lines · 170 tokens per session scan A 5984941bca7a

Subscribe to this mod's changes

qa-testing is a skill published in the GitHub repository rampstackco/claude-skills (822 stars, last pushed 9d ago), licensed MIT. It adds 170 tokens to every session and 3,248 once invoked, about $0.0009 per session on Opus 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-09-03.

Related

Other skills, from other repositories

accessibility-a11y

WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.

travisjneuman/.claude · 26 tokens

qa-expert

Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.

personamanagmentlayer/pcl · 53 tokens

unity-testing

Use when writing or structuring tests — EditMode vs PlayMode test decisions, test architecture, what to test in Unity, mocking strategies, and CI integration for Unity tests.

TheArcForge/Hades · 35 tokens

self-testing

E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…

shabaraba/vibing.nvim · 105 tokens

cypress-expert

Expert in Cypress testing framework, custom commands, fixtures, plugins, visual testing, and component testing. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or Cypress commands, or when the task involves Cypress Framework, Test Structure, Advanced Features, or Custom…

personamanagmentlayer/pcl · 68 tokens

jest-expert

Expert in Jest unit testing framework, mocks, snapshots, coverage reports, watch mode, and custom matchers. Use when the user mentions testing, unit testing, JavaScript, QA, mocking, or snapshots, or when the task involves Jest Framework, Test Structure, Advanced Features, or Basic Unit Tests.

personamanagmentlayer/pcl · 65 tokens