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 ChrisMckerracher/claude-dream-team --skill qagit clone --depth 1 https://github.com/ChrisMckerracher/claude-dream-teamWrote 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/chrismckerracher/claude-dream-team/qa)<a href="https://agentmods.dev/skills/chrismckerracher/claude-dream-team/qa"><img src="https://agentmods.dev/badge/skills/chrismckerracher/claude-dream-team/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/chrismckerracher/claude-dream-team/qa"><img src="https://agentmods.dev/badge/skills/chrismckerracher/claude-dream-team/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.00045 | $0.01040 |
| Opus 5 | $0.00023 | $0.00520 |
| Sonnet 5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
Quality Assurance 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Assurance Skill
Test Planning Framework
From Feature File to Test Plan
- Read the .feature file from
docs/features/ - For each Scenario, create a test case:
Test Case: [Scenario name] Type: e2e | api | unit Priority: critical | high | medium | low Steps: 1. [Given → setup step] 2. [When → action step] 3. [Then → assertion step] Expected: [What should happen] - Add edge cases not covered by the .feature file
- Identify which tests need browser vs. API-only
Test Priority Matrix
| User Impact | Likelihood | Priority |
|---|---|---|
| High | High | Critical - must pass |
| High | Low | High - test thoroughly |
| Low | High | Medium - automated |
| Low | Low | Low - best effort |
Playwright Test Patterns
Setup with Video Recording
import { test, expect } from '@playwright/test';
test.describe('Feature: [Name]', () => {
test.use({
video: 'on', // Always record video
screenshot: 'only-on-failure',
trace: 'retain-on-failure',
});
test('[Scenario name]', async ({ page }) => {
// Given
await page.goto('/path');
// When
await page.click('[data-testid="button"]');
// Then
await expect(page.locator('[data-testid="result"]')).toBeVisible();
});
});
Common Playwright Assertions
// Visibility
await expect(element).toBeVisible();
await expect(element).toBeHidden();
// Text content
await expect(element).toHaveText('expected');
await expect(element).toContainText('partial');
// Form state
await expect(input).toHaveValue('value');
await expect(checkbox).toBeChecked();
await expect(button).toBeEnabled();
// Navigation
await expect(page).toHaveURL(/pattern/);
await expect(page).toHaveTitle('Title');
// Network
const response = await page.waitForResponse('**/api/endpoint');
expect(response.status()).toBe(200);
Page Object Pattern
class LoginPage {
constructor(private page: Page) {}
async login(email: string, password: string) {
await this.page.fill('[data-testid="email"]', email);
await this.page.fill('[data-testid="password"]', password);
await this.page.click('[data-testid="submit"]');
}
async expectError(message: string) {
await expect(this.page.locator('[data-testid="error"]'))
.toHaveText(message);
}
}
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 · 171 lines · 45 tokens per session scan A c5e5f080c452
Quality Assurance is a skill published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,040 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 skills, from other repositories
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…