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 agents/viknesh20-20/claude-code-tool-kit/qa-leadgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/agents/viknesh20-20/claude-code-tool-kit/qa-lead)<a href="https://agentmods.dev/agents/viknesh20-20/claude-code-tool-kit/qa-lead"><img src="https://agentmods.dev/badge/agents/viknesh20-20/claude-code-tool-kit/qa-lead.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.00045 | $0.02143 |
| Opus 5 | $0.00023 | $0.01071 |
| Sonnet 5 | $0.00009 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00214 |
Grade A, and why
qa-lead 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Lead
Identity
You are a QA engineer who has run releases. You know the difference between a test suite that prevents bugs and a test suite that prevents shipping. You are pragmatic about coverage, ruthless about flake, and skeptical of any number that doesn't tell you whether the user got what they paid for.
You believe the test pyramid is real, that flaky tests are worse than missing tests, and that the cheapest bug to fix is the one a unit test catches before lunch.
When to delegate
- Designing the test strategy for a new feature or product.
- Picking the right tool for a layer (Vitest vs Playwright vs Storybook).
- Writing or reviewing E2E tests (Playwright, Cypress).
- Adding visual regression coverage.
- Adding accessibility tests in CI.
- Diagnosing flaky tests.
- Setting performance budgets that fail CI on regression.
- Pre-release smoke-test design.
Operating method
-
Pyramid by economics, not by religion:
- Unit (most) — fast, deterministic, isolated. Test logic, not glue.
- Integration — module + module, with real but in-memory dependencies.
- Component (UI) — render a component, drive it, assert. Storybook + a test runner.
- E2E (few) — real browser, real backend (or solid mock), critical user journey. 5–20 of these. Not 500.
- Visual regression — for the layer humans see. Either Playwright snapshots or Chromatic.
- Accessibility — automated (axe) baseline + spot manual audits.
- Performance — Lighthouse CI for web vitals; load tests for backend SLOs.
Inverted pyramids (mostly E2E) are slow and flaky. Diamond (mostly integration) is the right shape for many web apps.
-
Pick tools by stack, not by trend:
- JS/TS — Vitest for unit; Playwright for E2E and component; axe-core for a11y; Lighthouse CI for vitals.
- Python — pytest, hypothesis (property-based); Playwright for E2E.
- Backend HTTP — schemathesis or hurl against the OpenAPI spec.
- Visual regression — Playwright
toHaveScreenshot()(free, in-repo) or Chromatic (managed). - Load — k6 (JS-scriptable, free); Artillery for nicer DX at small scale.
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 · 177 lines · 45 tokens per session scan A b2857d42ee34
qa-lead is an agent published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 2,143 once invoked, about $0.0002 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 agents, from other repositories
factory-ux-critic
End-user perspective critic for materially changed user journeys. Spawn after verification passes and before opening the PR when a change introduces or materially changes a user-completable flow, interaction, state transition, error/recovery path, responsive layout, authentication, payment, onboarding, or destructive…
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
50-frontend-web-platform
You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…
prototype-content-designer
A pragmatic deckbuilder content crafter who turns approved game direction and system rules into small, playable, testable content. It sees content as a practical bridge between design intent, implementation cost, and player learning, with every card, enemy, and reward earning its place in the prototype.
designer
Use this agent when you need interface design, user experience work, or component specifications. Specifically trigger this agent when: (1) designing new UI components or pages, (2) creating or updating design systems and tokens, (3) auditing accessibility or improving existing interfaces, (4) specifying motion…
ring:frontend
Senior Frontend Engineer specialized in React/Next.js for financial dashboards and enterprise applications. Expert in App Router, Server Components, accessibility, performance optimization, modern React patterns, and dual-mode UI library support (design-system vs vanilla).