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 utsavanand/uv-suite --skill uvs-qagit clone --depth 1 https://github.com/utsavanand/uv-suiteWrote 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/utsavanand/uv-suite/uvs-qa)<a href="https://agentmods.dev/skills/utsavanand/uv-suite/uvs-qa"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-qa/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/utsavanand/uv-suite/uvs-qa"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-qa.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.00071 | $0.03055 |
| Opus 5.5 | $0.00028 | $0.01222 |
| Sonnet 5.5 | $0.00014 | $0.00611 |
| Haiku 4.5 | $0.00007 | $0.00305 |
Grade A, and why
uvs-qa 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 2mo 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.
- Bash(curl -sf *) How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Target
$ARGUMENTS
Parse $ARGUMENTS:
- First positional token without
--prefix → app URL (defaults tohttp://localhost:3000if not given). --tier quick|standard|exhaustive→ tier (defaults tostandard).--baseline <path>→ path to a priorqa-state.mdfor health-score delta (defaults touv-out/qa-state.md, the flat pointer to the latest run, if present).
Session output directory
Write QA artifacts under this directory (scoped to the current session). The
<session-output-dir>/qa/<ts>/ paths below all resolve under it:
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-session.sh
Stable flat pointer maintained for /uvs-commit and /ship:
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-pointer.sh qa-state.md qa/state.md
Project context
!cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found"
Detected test framework
!(test -f playwright.config.ts && echo "playwright") || (test -f playwright.config.js && echo "playwright") || (test -f vitest.config.ts && echo "vitest") || (test -f jest.config.js && echo "jest") || (grep -l '"jest"' package.json 2>/dev/null && echo "jest") || echo "none-detected"
Tier definitions
| Tier | Viewports | Pages | Console capture | Fix bugs | Generate regression tests |
|---|---|---|---|---|---|
quick |
1 (desktop 1440×900) | Top-level entry + 1 deep link | Yes | No (report only) | No |
standard |
2 (desktop 1440×900, mobile 390×844) | Entry + every link in nav + 2 deep flows | Yes | Only critical severity |
When framework detected |
exhaustive |
3 (desktop, tablet 1024×768, mobile) | Every reachable page from nav + 3 deep flows + edge-case inputs | Yes | All critical + high |
Yes when framework detected |
If $ARGUMENTS doesn't specify a tier, default to standard.
Orchestration procedure
Execute these steps in order.
Step 1 — Setup
- Confirm Playwright MCP is reachable (
mcp__playwright__browser_*tools available). If not, stop and tell user to enable the Playwright MCP server. - Verify the target URL is reachable:
curl -sf <url> > /dev/null. If not, stop and ask user to start the dev server. - Create output directory:
mkdir -p <session-output-dir>/qa/<ISO-timestamp>/screenshots(the<session-output-dir>printed above). - If framework detected, note its config path; you'll write regression tests against it later.
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.
- 2mo ago First seen · 275 lines · 71 tokens per session scan A 0085da5390fc
uvs-qa is a skill published in the GitHub repository utsavanand/uv-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 3,055 once invoked, about $0.0003 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.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
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.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…