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/whitebeardit/.cursor/skill-qa-code-reviewnpx skills add whitebeardit/.cursor --skill skill-qa-code-reviewgit clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/skill-qa-code-review)<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-qa-code-review"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-qa-code-review.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.00061 | $0.00914 |
| Opus 5 | $0.00030 | $0.00457 |
| Sonnet 5 | $0.00012 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
qa-code-review 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Code Review
This skill defines how to review QA Playwright code (specs, test-data, fixtures) by considering the perspective of each QA subagent, then consolidating their concerns into one report focused on manutenção, qualidade e padronização.
When to Use
- User asks for a code review of specs, test-data, or flow.
- User asks "o que acha do código?" or "revise esse teste".
- User wants a consolidated improvement list from the point of view of the project's QA standards.
Process
- Identify scope: What is under review? (single spec, whole flow, test-data, fixtures.)
- Apply each relevant QA perspective by reading and applying the criteria from:
- Conventions (maintain): skill-qa-playwright-maintain-conventions — imports, test-data usage, structure, locators.
- Fixtures (add-fixture): skill-qa-playwright-add-fixture — whether fixtures would reduce duplication or improve structure.
- Flow (add-flow): skill-qa-playwright-add-new-flow — when reviewing a flow: folders, inputs, baseURL, naming.
- Optionally consider:
- Test-data: skill-qa-playwright-add-test-data — if the review involves inputs.json, builder.ts.
- Frontend-friendly: skill-frontend-qa-friendly — locators, accessibility, stability.
- Produce a single report with the structure below.
Output Structure
Produce the review in this order:
1. Manutenção (conventions)
- Checklist from maintain skill: imports from fixtures, test-data vs hardcode, directory structure, baseURL.
- Explicit: ✅ atende / ⚠️ atenção / ❌ não atende, with short reason.
2. Qualidade
- Locators: resilient (getByRole, getByLabel, getByText) vs brittle (XPath por posição, classes).
- Assertions: web-first, timeouts adequados, critérios de sucesso claros.
- Legibilidade: Arrange–Act–Assert, comentários úteis, nome do teste descritivo.
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 · 64 lines · 61 tokens per session scan A 94308a243a74
qa-code-review is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 914 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
e2e-write-visual-test
Use when writing a Playwright visual regression (screenshot comparison) test, tagging a test @visual, generating or updating baseline screenshots, running visual tests locally, or debugging a failing screenshot comparison in CI.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…