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/unit-testingnpx skills add DynamoDS/DynamoHome --skill unit-testinggit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWhat 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.00852 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
unit-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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Testing Skills – DynamoHome
Stack
- Runner: Jest 29 with
ts-jestpreset - DOM:
jest-environment-jsdom - Component testing:
@testing-library/react15 - Run tests:
npm run test:unit(targetstests/unit/) - Coverage output:
./coverage/(lcov + text reporters) - Coverage target: 100% for all files under
src/
Test file location
tests/
unit/
App.test.tsx # Existing app-level test
ComponentName.test.tsx # One test file per component — place new tests here
jest.setup.ts # Applied via setupFilesAfterEnv — do not modify
__mocks__/
chromeMock.ts # Auto-applied: mocks window.chrome.webview globals
fileMock.ts # Auto-applied: mocks image imports
styleMock.ts # Auto-applied: mocks CSS module imports
Mocks — what's already set up
The chromeMock.ts is applied globally in jest.setup.ts. It mocks:
window.chrome.webview.hostObjects.scriptObject(all backend methods)- Global callbacks like
window.receiveGraphDataFromDotNet
Do not re-mock these in individual test files — they're already available.
CSS Modules are mocked by tests/__mocks__/styleMock.ts, which returns an empty object — styles['class-name'] returns undefined in tests (class names are not asserted on).
Writing a test
import React from 'react';
import { render, screen, fireEvent } from '@testing-library/react';
import { IntlProvider } from 'react-intl';
import messages from '../../src/locales/en.json';
import { CardItem } from '../../src/components/Common/CardItem';
// Wrap with IntlProvider for components using FormattedMessage
const renderWithIntl = (ui: React.ReactElement) =>
render(
<IntlProvider locale="en" messages={messages}>
{ui}
</IntlProvider>
);
describe('CardItem', () => {
it('renders the title', () => {
renderWithIntl(<CardItem titleText="My Graph" imageSrc="" onClick={jest.fn()} />);
expect(screen.getByText('My Graph')).toBeInTheDocument();
});
it('calls onClick when clicked', () => {
const handleClick = jest.fn();
renderWithIntl(<CardItem titleText="My Graph" imageSrc="" onClick={handleClick} />);
fireEvent.click(screen.getByRole('button'));
expect(handleClick).toHaveBeenCalledTimes(1);
});
});
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.
- yesterday First seen · 102 lines · 0 tokens per session scan A f677bf0b6142
unit-testing is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…