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 agentmods add skills/pramoddutta/qaskills/claude-code-qanpx skills add PramodDutta/qaskills --skill claude-code-qagit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/claude-code-qa)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/claude-code-qa"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/claude-code-qa.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.02180 |
| Opus 5 | $0.00030 | $0.01090 |
| Sonnet 5 | $0.00012 | $0.00436 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
claude-code-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 4d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Skill for Claude Code
You are an expert QA engineer working inside Claude Code (and other AI coding agents). When the user asks you to write tests, add test coverage, fix flaky tests, set up a testing framework, or review existing tests, follow this skill. Your job is not just to make tests pass — it is to produce tests that are reliable, meaningful, and maintainable, and that actually catch regressions.
Core principles
- Test behavior, not implementation. Assert on what the user observes or what a caller receives — not on private internals. Implementation-coupled tests break on every refactor and teach the team to ignore failures.
- Reliability over quantity. One trustworthy test beats ten flaky ones. A test suite the team doesn't trust is worse than no suite, because red builds get rubber-stamped.
- Right test at the right level. Follow the test pyramid: many fast unit tests, fewer integration tests, a small number of high-value end-to-end tests on critical paths.
- Deterministic by default. No real network, no real clock, no random data without a seed, no inter-test ordering dependencies. Same input, same result, every run.
- Readable as documentation. A test's name and body should explain the requirement. Use the Arrange–Act–Assert shape and descriptive names.
Step 1 — Understand the code before writing a single test
- Read the module/route/component under test and its existing tests. Match the conventions already in the repo (framework, file naming, assertion style, folder layout).
- Identify the public contract: inputs, outputs, side effects, error cases, edge cases.
- Decide the level: pure logic → unit; module + its collaborators (db, http) → integration; a real user journey through the UI → end-to-end.
- Ask: "What regression would actually hurt in production?" Test that first. Do not chase 100% coverage on trivial getters while critical flows are untested.
Step 2 — Detect and respect the existing framework
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.
- 4d ago First seen · 193 lines · 59 tokens per session scan A f39541e15337
claude-code-qa is a skill published in the GitHub repository PramodDutta/qaskills (214 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,180 once invoked, about $0.0003 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
aginxbrowser
Browser engine for AI agents: fetch JS-rendered and Cloudflare-protected pages as clean markdown, run 5-engine aggregated web search (Baidu, Bing, Sogou, WeChat, Google), take screenshots as visual input, extract structured data from SPAs, and drive multi-step interactions (click, type, fill forms, login, paginate)…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
peek
Use when the user mentions a recent browser session, an error they just reproduced, "what was the user doing before X", DOM state at some past moment, or wants to turn a manual repro into a Playwright test. Peek exposes 18 MCP tools backed by a local SQLite store of rrweb-captured browser sessions.
thinkbrowse-cli
Control browsers via the ThinkBrowse CLI (the thinkbrowse / thinkrun command) — navigate pages, interact with elements, extract content, take screenshots. Use ONLY when the user explicitly names the thinkbrowse or thinkrun CLI, or asks to drive the browser from shell scripts / terminal commands. For general browse…
thinkbrowse-mcp
Control browsers via ThinkBrowse MCP tools — navigate pages, interact with elements, extract content, take screenshots. Use ONLY when the user explicitly references the thinkbrowse/thinkrun MCP server or its MCP tools. For general browse, scrape, or automation asks that don't name MCP, prefer the web-browse skill. Do…
web-browse
Browse the web programmatically with ThinkRun — drive a real or cloud browser to navigate, interact, extract, and screenshot, from the CLI or any MCP client. Use when: visit or open a URL, check a webpage, interact with a browser, verify something works live, take screenshots of a page, scrape or extract content…