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 commands/rcdelacruz/claude-code-agents/workflow-qa-e2egit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWhat 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.00009 | $0.03315 |
| Opus 5 | $0.00005 | $0.01657 |
| Sonnet 5 | $0.00002 | $0.00663 |
| Haiku 4.5 | $0.00001 | $0.00331 |
Grade B, and why
workflow-qa-e2e scanned grade B 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch('http://localhost:3000/api/test/users', { method: 'POST', How it starts
The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are in E2E TESTING MODE.
Use qa-tester agent to write Playwright end-to-end tests.
E2E Testing Workflow
1. Test Planning (10 mins)
Identify Critical User Flows
- User authentication (signup, login, logout)
- Core feature usage (create, read, update, delete)
- Payment/checkout flows
- Form submissions
- Navigation and routing
- Error scenarios
Define Test Scenarios
// User Story: User can create and publish a blog post
Scenarios:
1. Happy path: Create and publish post successfully
2. Validation: Form validation prevents invalid input
3. Authorization: Only authenticated users can create posts
4. Error handling: Network error shows appropriate message
5. Edge case: Very long title/content
2. Playwright Setup (5 mins)
Install Playwright
npm install -D @playwright/test
npx playwright install
playwright.config.ts
import { defineConfig, devices } from '@playwright/test'
export default defineConfig({
testDir: './e2e',
fullyParallel: true,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 2 : 0,
workers: process.env.CI ? 1 : undefined,
reporter: 'html',
use: {
baseURL: 'http://localhost:3000',
trace: 'on-first-retry',
screenshot: 'only-on-failure',
},
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'] },
},
{
name: 'firefox',
use: { ...devices['Desktop Firefox'] },
},
{
name: 'mobile',
use: { ...devices['iPhone 13'] },
},
],
webServer: {
command: 'npm run dev',
url: 'http://localhost:3000',
reuseExistingServer: !process.env.CI,
},
})
3. Page Object Model (15 mins)
Create Page Objects for Reusability
// e2e/pages/login.page.ts
import { Page, Locator } from '@playwright/test'
export class LoginPage {
readonly page: Page
readonly emailInput: Locator
readonly passwordInput: Locator
readonly submitButton: Locator
readonly errorMessage: Locator
constructor(page: Page) {
this.page = page
this.emailInput = page.getByLabel('Email')
this.passwordInput = page.getByLabel('Password')
this.submitButton = page.getByRole('button', { name: 'Sign in' })
this.errorMessage = page.getByRole('alert')
}
async goto() {
await this.page.goto('/login')
}
async login(email: string, password: string) {
await this.emailInput.fill(email)
await this.passwordInput.fill(password)
await this.submitButton.click()
}
async expectError(message: string) {
await expect(this.errorMessage).toContainText(message)
}
}
// e2e/pages/posts.page.ts
export class PostsPage {
readonly page: Page
readonly createButton: Locator
readonly titleInput: Locator
readonly contentInput: Locator
readonly publishButton: Locator
constructor(page: Page) {
this.page = page
this.createButton = page.getByRole('button', { name: 'New Post' })
this.titleInput = page.getByLabel('Title')
this.contentInput = page.getByLabel('Content')
this.publishButton = page.getByRole('button', { name: 'Publish' })
}
async goto() {
await this.page.goto('/posts')
}
async createPost(title: string, content: string) {
await this.createButton.click()
await this.titleInput.fill(title)
await this.contentInput.fill(content)
await this.publishButton.click()
}
async getPostByTitle(title: string) {
return this.page.getByRole('article', { name: title })
}
}
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.
- 2d ago First seen · 495 lines · 9 tokens per session scan B da6ea88ed650
workflow-qa-e2e is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 3,315 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
e2e
使用 Playwright 对 Web UI 进行端到端测试(支持视频录制、Trace 录制、控制台/网络日志捕获).
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
review
Compare a reference design against an implementation. Accepts Figma URL, image file, or browser URL as reference.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.