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 RudraDudhat2509/claude-skills --skill qa-checklistgit clone --depth 1 https://github.com/RudraDudhat2509/claude-skillsWrote 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/rudradudhat2509/claude-skills/qa-checklist)<a href="https://agentmods.dev/skills/rudradudhat2509/claude-skills/qa-checklist"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/qa-checklist/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/rudradudhat2509/claude-skills/qa-checklist"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/qa-checklist.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.00024 | $0.01165 |
| Opus 5 | $0.00012 | $0.00583 |
| Sonnet 5 | $0.00005 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
qa-checklist 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Checklist Generator
When this skill is invoked:
- Generate and split the checklist into two parts: Automated (subagent runs) and Manual (user runs)
- Dispatch a subagent to execute all automated checks immediately
- Present the manual checklist to the user
Step 1 — Gather session context
- Run
git log --onelineto see what was committed this session - Run
git diff <baseline>..HEAD --statto see what files changed - Get a real
brandIdfrom the database:node -e "const {PrismaClient}=require('@prisma/client');const p=new PrismaClient();p.brand.findFirst().then(b=>console.log(b?.id)).finally(()=>p.\$disconnect())" - For each meaningful change, derive testable checks
Step 2 — Classify every check
Automated (subagent runs) — anything verifiable without human eyes or interaction:
- API routes: GET/POST/PATCH/DELETE calls with PowerShell, checking response shape and values
- Auth flows: login, logout, cookie lifecycle, 401 on unauthenticated requests
- Validation rejections: wrong type, missing field, empty string
- Unit/integration test suite:
npm test - TypeScript check:
npx tsc --noEmit - File content assertions: confirm console.logs removed, no banned patterns
estimateCost,weekKeyForDate, and other pure exported functions vianpx tsx -e- DB persistence: write then read back to confirm record was created
Manual (user runs) — anything that requires eyes, clicks, or live external services:
- UI renders correctly (layout, icons, colours, loading states)
- Error states shown inline (e.g. "Invalid password" text appearing on the page)
- Redirect behaviour after form submit
- Dashboard tab content looks correct (charts, tables populated)
- AI-generated content quality (blog post, ad copy, chat response)
- Budget breach → alert banner appears site-wide
- AlertBanner dismiss interaction
- Journey step execution with real delays
- WhatsApp message delivery
- Anything requiring a live external service (Shopify API, Meta API, WhatsApp Cloud)
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.
- 11d ago First seen · 126 lines · 24 tokens per session scan A d3dc50bc2be4
qa-checklist is a skill published in the GitHub repository RudraDudhat2509/claude-skills (2 stars, last pushed 18d ago), licensed MIT. It adds 24 tokens to every session and 1,165 once invoked, about $0.0001 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-31.
Other skills, from other repositories
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
safe-rename
Workflow for safely renaming symbols (functions, types, classes, interfaces, constants, variables) across a codebase. Uses repomap, batchsymbols, and buildcheck to ensure every consumer is updated and nothing breaks.
test-file-split
Protocol for splitting test files that approach or exceed the FR-006 500-line limit (enforced in CI by scripts/check-test-file-cap.ts as a diff-scoped ratchet). Covers describe-block extraction, shared helper management, pure-function extraction, mock isolation verification, and cascading-split detection. Load when a…
vs-chat
Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses.