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 RadOrigin-LLC/RAD-Claude-Skills --skill chrome-ext-testinggit clone --depth 1 https://github.com/RadOrigin-LLC/RAD-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/radorigin-llc/rad-claude-skills/chrome-ext-testing)<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/chrome-ext-testing"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/chrome-ext-testing/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/radorigin-llc/rad-claude-skills/chrome-ext-testing"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/chrome-ext-testing.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.00101 | $0.00995 |
| Opus 5 | $0.00051 | $0.00498 |
| Sonnet 5 | $0.00020 | $0.00199 |
| Haiku 4.5 | $0.00010 | $0.00100 |
Grade A, and why
chrome-ext-testing 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome Extension Testing
Extension testing spans three tiers: unit tests for pure logic, integration tests for messaging/storage/UI, and E2E tests for multi-context journeys. Vitest with @webext-core/fake-browser handles the first two. Playwright handles E2E with real browser contexts.
Framework Selection
| Tier | Framework | Why |
|---|---|---|
| Unit | Vitest | Fast, Vite-native, works with WXT |
| Integration | Vitest Browser Mode | Real browser DOM for authentic behavior |
| E2E | Playwright | Isolated browser contexts, Shadow DOM piercing |
Unit Testing
Test pure logic, utilities, and API-mocked code with @webext-core/fake-browser:
// vitest.config.ts
import { defineConfig } from 'vitest/config';
export default defineConfig({
test: {
setupFiles: ['./test/setup.ts'],
},
});
// test/setup.ts
import { fakeBrowser } from '@webext-core/fake-browser';
vi.stubGlobal('browser', fakeBrowser);
vi.stubGlobal('chrome', fakeBrowser);
What to test:
- Algorithms, formatting helpers, data transformers
- Storage read/write logic (fake-browser polyfills chrome.storage)
- Message routing logic (fake-browser polyfills chrome.runtime)
- Utility functions
import { describe, it, expect } from 'vitest';
describe('storage utils', () => {
it('reads with defaults', async () => {
const result = await chrome.storage.local.get({ theme: 'light' });
expect(result.theme).toBe('light');
});
it('persists and retrieves data', async () => {
await chrome.storage.local.set({ count: 42 });
const { count } = await chrome.storage.local.get('count');
expect(count).toBe(42);
});
});
Integration Testing
Test UI interactions, messaging, and storage flows:
- Use Vitest Browser Mode for authentic DOM/CSS behavior
- Test loading, error, and empty states
- Test keyboard navigation and accessibility
- Mock external APIs and network requests
describe('Popup', () => {
it('loads settings from storage', async () => {
await chrome.storage.local.set({ theme: 'dark' });
render(<Popup />);
expect(screen.getByRole('button', { name: /dark/i })).toBeInTheDocument();
});
it('saves settings on change', async () => {
render(<Popup />);
fireEvent.click(screen.getByRole('button', { name: /toggle/i }));
const { theme } = await chrome.storage.local.get('theme');
expect(theme).toBe('dark');
});
});
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 132 lines · 101 tokens per session scan A a527f7fd9b05
chrome-ext-testing is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 23d ago), licensed Apache-2.0. It adds 101 tokens to every session and 995 once invoked, about $0.0005 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
vibe-behavioral-test-capture
Builds an executable safety net of characterization tests by integrating browser flow recording, API payload snapshotting, DOM state captures, network traces, and mock fixture generation.
test-writing
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
testing-strategy
Test strategy and quality engineering — the test pyramid, what to test at each layer, meaningful coverage policy, integration and contract testing, E2E for critical journeys, test data and fixtures, flaky-test control, mutation testing, load and security testing, and CI gating. Use when the user says "tests"…
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug…
audit-ui-e2e
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to…
capture-screens
Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting…