DynamoHome: Skill for Claude Code

.claude/skills/unit-testing/SKILL.md

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

Project-specific guidance for unit testing a React and TypeScript application with Jest. Unit tests check small pieces of code, such as individual components, in isolation.

In plain words
What is it for?
Use it to add or update component tests, use the project’s existing mocks, and measure coverage of the source files.
Why use it?
It tells you where tests belong, how to run them, and which browser and file mocks are already available, reducing setup mistakes and duplicate work.

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 →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import messages from '../../src/locales/en.json';.

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/unit-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 unit-testing

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/dynamods/dynamohome/unit-testing"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/unit-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 852 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.00852
Opus 5.5 $0.00000 $0.00341
Sonnet 5.5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

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

Security

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 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/unit-testing/SKILL.md · 102 lines

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-jest preset
  • DOM: jest-environment-jsdom
  • Component testing: @testing-library/react 15
  • Run tests: npm run test:unit (targets tests/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);
  });
});

Read the full file on GitHub · 102 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 · 102 lines · 0 tokens per session scan A f677bf0b6142

Subscribe to this mod's changes

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