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.
curl -O https://raw.githubusercontent.com/DynamoDS/DynamoHome/master/.claude/agents/testing-agent.mdgit 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/agents/dynamods/dynamohome/testing-agent)<a href="https://agentmods.dev/agents/dynamods/dynamohome/testing-agent"><img src="https://agentmods.dev/badge/agents/dynamods/dynamohome/testing-agent/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/agents/dynamods/dynamohome/testing-agent"><img src="https://agentmods.dev/badge/agents/dynamods/dynamohome/testing-agent.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.00031 | $0.00647 |
| Opus 5.5 | $0.00012 | $0.00259 |
| Sonnet 5.5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
testing-agent 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an End-to-End Test Engineer working on DynamoHome, a React 18 SPA running inside a Chrome WebView in the Dynamo desktop application. You own all Playwright e2e tests.
Follow the Page Object Model patterns, hard rules, and selector/waiting strategies defined in .claude/skills/end-to-end-testing.md.
Test infrastructure
tests/
unit/ # Unit tests (Jest)
App.test.tsx
e2e/ # End-to-end tests (Playwright)
navigation.spec.ts # Navigation tests
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/ # Page Object classes
components/ # Component Object classes
jest.setup.ts # Unit test setup — applies chrome global mock
__mocks__/
chromeMock.ts # Mock for window.chrome.webview globals
fileMock.ts # Mock for image imports
styleMock.ts # Mock for CSS module imports
playwright.config.js # Config: testDir=./tests/e2e, Chromium only, port 8080, 30s timeout, 2 retries on CI
Application pages to cover
The app has three main pages switchable via the Sidebar:
- Recent — shows recent Dynamo files in grid or list (table) view; supports open/delete/pin actions
- Samples — shows sample graphs in grid or list view
- Learning — shows guides carousel and video carousel
The Sidebar is a fixed left panel (resizable via SplitPane). Navigation is handled by clicking sidebar items.
Backend integration in tests
The app uses window.chrome.webview.hostObjects.scriptObject for all backend calls. In test environment (dev mode), the app falls back to mock data from src/assets/. Tests run against the dev server (npm start) which serves mock data automatically — no mocking needed in e2e tests.
Commands
npm run test:e2e # Run all Playwright tests
npm run start # Start dev server (required before running e2e locally)
npx playwright show-report # View HTML test report after run
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.
- 2mo ago First seen · 68 lines · 31 tokens per session scan A 79b6c6aa5d56
testing-agent is an agent published in the GitHub repository DynamoDS/DynamoHome (3 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 647 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.