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.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/playwright-test-generator)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/playwright-test-generator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/playwright-test-generator/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/agents/random6913/claude-code-superkit/playwright-test-generator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/playwright-test-generator.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.00017 | $0.01950 |
| Opus 5.5 | $0.00007 | $0.00780 |
| Sonnet 5.5 | $0.00003 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
playwright-test-generator 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 1mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Test Generator — SocialApp Admin Panel
Generate Playwright e2e tests for the admin frontend panel following SocialApp conventions and Playwright best practices.
Phase 0: Load Project Context
Read if exists:
CLAUDE.mdorAGENTS.md— project conventionsdocs/architecture/— relevant architecture docs for the task at hand
Use this context to:
- Know project-specific conventions and patterns
- Identify documented rules to check with HIGH confidence
- Understand the tech stack and framework in use
Project Context
- Stack: React 19 + TypeScript 5.9 + Vite 7 + Tailwind CSS 3.4 + Radix UI
- Routing: state-based (
activePagein AppShell), NOT React Router - API layer:
requestJSON<T>()through live-only API clients (*ApiLive.ts+*ApiClient.ts) - Test runner:
cd adminpanel/frontend && npm run test:e2e - Config:
adminpanel/frontend/playwright.config.ts(baseURLhttp://127.0.0.1:4173, Chromium) - Existing tests:
adminpanel/frontend/tests/admin-smoke.spec.ts - Admin pages: Overview, Users, Moderation, Engagement, Monetization, Ads, Settings, Roles & Access, System
Test Patterns
Page Object Model
Every page under test gets a Page Object class. Place them in adminpanel/frontend/tests/pages/.
// tests/pages/users-page.ts
import { type Locator, type Page, expect } from '@playwright/test';
export class UsersPage {
readonly page: Page;
readonly heading: Locator;
readonly searchInput: Locator;
readonly userTable: Locator;
constructor(page: Page) {
this.page = page;
this.heading = page.locator('header').getByRole('heading', { level: 2, name: 'Users' });
this.searchInput = page.getByPlaceholder('Search users...');
this.userTable = page.getByRole('table');
}
async navigate() {
await this.page.locator('aside').getByRole('button', { name: 'Users' }).click();
await expect(this.heading).toBeVisible();
}
async searchUser(query: string) {
await this.searchInput.fill(query);
await this.searchInput.press('Enter');
}
}
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.
- 1mo ago First seen · 234 lines · 17 tokens per session scan A 21bd33460194
playwright-test-generator is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 1,950 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.