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/dlupiak/claude-session-dashboard/testingnpx skills add dlupiak/claude-session-dashboard --skill testinggit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWrote 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/dlupiak/claude-session-dashboard/testing)<a href="https://agentmods.dev/skills/dlupiak/claude-session-dashboard/testing"><img src="https://agentmods.dev/badge/skills/dlupiak/claude-session-dashboard/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.00019 | $0.00313 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
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 2d 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.
What it actually says
Testing Patterns
Vitest (Unit + Integration)
- Config lives in
apps/web/vite.config.ts(no separate vitest.config) - Run:
npm run testfromapps/web/ - Run single file:
npx vitest run path/to/file.test.ts
vi.mock Gotcha (IMPORTANT)
vi.mock() is hoisted to the top of the file. You CANNOT reference variables declared above it:
// BAD — will be undefined
const mockFn = vi.fn()
vi.mock('./module', () => ({ doThing: mockFn }))
// GOOD — define inline
vi.mock('./module', () => ({ doThing: vi.fn() }))
import { doThing } from './module'
// Now doThing is the mock — use it for assertions
Rules
- Test behavior, not implementation
- Prefer integration tests over unit tests
- Mock external services, not internal functions
- "close timed out" warning after Vitest is a known nitro issue — ignore
Playwright (E2E)
- Config:
apps/web/playwright.config.ts - Tests:
apps/web/e2e/ - Run:
npm run test:e2efromapps/web/ - Use
page.getByRole(),page.getByText()over CSS selectors
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.
- 2d ago First seen · 39 lines · 19 tokens per session scan A 6aca8ba84a40
testing is a skill published in the GitHub repository dlupiak/claude-session-dashboard (66 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 313 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
test-generator
完整：uv run ruff check src/; uv run mypy src/ --ignore-missing-imports; uv run bandit -r src/ -ll.
chrome-ext-testing
This skill should be used when writing or setting up tests for a Chrome extension. Trigger when: "test chrome extension", "extension unit test", "extension e2e test", "Vitest extension", "Playwright extension", "@webext-core/fake-browser", "test content script", "test service worker", "test messaging", "test storage"…
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.
prodtest
Senior-QA test pass on a newly implemented feature. Detects the project's real test stack, writes unit and functional/integration tests, then drives the running app with Playwright for end-to-end coverage, saving screenshots to a gitignored folder for human review. Asks upfront whether found bugs should be fixed or…
testing-quality-engineering
Use this capability for test plans, unit/integration/e2e tests, contract tests, property tests, snapshot strategy, mocks, test data, coverage, flaky tests, regression suites, quality gates, AI evals, and release verification. Trigger on test, QA, coverage, flaky, regression, e2e, integration, contract test, unit test…