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 skills/dynamods/dynamohome/end-to-end-testingnpx skills add DynamoDS/DynamoHome --skill end-to-end-testinggit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWrote 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/dynamods/dynamohome/end-to-end-testing)<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="Measured on agentmods" 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 | $0.00000 | $0.01117 |
| Opus 5 | $0.00000 | $0.00558 |
| Sonnet 5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
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 5d 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 — 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.tsfiles intests/e2e/) - Prerequisite:
npm run startmust be running (or configure thewebServerin 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();
}
}
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.
- 5d ago First seen · 144 lines · 0 tokens per session scan A c55aaa74cefc
end-to-end-testing is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 18d 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.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…