DynamoHome: Skill for Claude Code

.claude/skills/end-to-end-testing/SKILL.md

end-to-end-testing is a skill for Claude Code from DynamoDS/DynamoHome. It costs 0 tokens per session (1,117 once invoked), scanned A, original, MIT.

Project-specific guidance for end-to-end testing with Playwright. End-to-end tests run the application in a browser and check complete user actions, such as navigation and page interactions.

In plain words
What is it for?
Use it to test flows across pages such as Recent, Samples, Learning, and the sidebar, while keeping selectors and browser actions inside reusable page classes.
Why use it?
It defines the required browser setup, folders, page-object pattern, server address, timeouts, and test commands so tests follow the project’s conventions.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is DynamoDS/DynamoHome's own configuration. It tells Claude Code how to work on DynamoHome itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything DynamoHome configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DynamoDS/DynamoHome. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DynamoDS/DynamoHome/master/.claude/skills/end-to-end-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/DynamoDS/DynamoHome

Made for: Claude Code.

Wrote 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.

agentmods badge for end-to-end-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/dynamods/dynamohome/end-to-end-testing/github.svg)](https://agentmods.dev/skills/dynamods/dynamohome/end-to-end-testing)
Your own site
<a href="https://agentmods.dev/skills/dynamods/dynamohome/end-to-end-testing"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/end-to-end-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.

agentmods 80×15 button for end-to-end-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/dynamods/dynamohome/end-to-end-testing"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/end-to-end-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,117 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01117
Opus 5.5 $0.00000 $0.00447
Sonnet 5.5 $0.00000 $0.00223
Haiku 4.5 $0.00000 $0.00112

Measured 2mo ago against content hash c55aaa74cefc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

end-to-end-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 2mo 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.

.claude/skills/end-to-end-testing/SKILL.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

End-to-End Testing – DynamoHome

Playwright configuration

  • Config file: playwright.config.js (testDir: './tests/e2e')
  • Browser: Chromium only (Desktop Chrome profile)
  • Base URL: http://localhost:8080 (dev server must be running)
  • Timeouts: 30s per test, 5s for expect assertions
  • Retries: 2 on CI, 0 locally
  • Run tests: npm run test:e2e (targets all *.spec.ts files in tests/e2e/)
  • Prerequisite: npm run start must be running (or configure the webServer in config which auto-starts it)

Required folder structure

tests/
  e2e/
    navigation.spec.ts       # Navigation tests — NO selectors, NO page.locator()
    sidebar.spec.ts          # Sidebar dropdown tests
    recent.spec.ts           # Recent page tests
    samples.spec.ts          # Samples page tests
    learning.spec.ts         # Learning page and carousel tests
    pages/
      RecentPage.ts          # Page class for Recent files page
      SamplesPage.ts         # Page class for Samples page
      LearningPage.ts        # Page class for Learning page
    components/
      Sidebar.ts             # Sidebar navigation component class
  unit/
    App.test.tsx             # Unit tests — separate from e2e
  jest.setup.ts              # Jest setup (not used by Playwright)
  __mocks__/                 # Jest mocks (not used by Playwright)

Page Object Model — mandatory pattern

Page class

// tests/e2e/pages/RecentPage.ts
import { Page, Locator } from '@playwright/test';

export class RecentPage {
  private readonly gridViewToggle: Locator;
  private readonly listViewToggle: Locator;
  private readonly graphCards: Locator;

  constructor(private page: Page) {
    this.gridViewToggle = page.locator('[data-testid="grid-view-toggle"]');
    this.listViewToggle = page.locator('[data-testid="list-view-toggle"]');
    this.graphCards = page.locator('[data-testid="graph-card"]');
  }

  async switchToGridView(): Promise<void> {
    await this.gridViewToggle.click();
  }

  async switchToListView(): Promise<void> {
    await this.listViewToggle.click();
  }

  async getGraphCount(): Promise<number> {
    return this.graphCards.count();
  }

  async openGraphByName(name: string): Promise<void> {
    await this.graphCards.filter({ hasText: name }).dblclick();
  }
}

Read the full file on GitHub · 144 lines

Changes

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.

  1. 2mo ago First seen · 144 lines · 0 tokens per session scan A c55aaa74cefc

Subscribe to this mod's changes

end-to-end-testing is a skill published in the GitHub repository DynamoDS/DynamoHome (3 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,117 tokens. 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.

Related

Other skills, from other repositories

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens