Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingnpx agentmods add skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-testingWrote 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/salesforcecommercecloud/b2c-developer-tooling/sfnext-testing)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-testing"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-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.
<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-testing"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00208 | $0.02089 |
| Opus 5.5 | $0.00083 | $0.00836 |
| Sonnet 5.5 | $0.00042 | $0.00418 |
| Haiku 4.5 | $0.00021 | $0.00209 |
Grade A, and why
sfnext-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 15d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Storefront Next
Three layers, all shipped in your project (see docs/README-TESTS.md, docs/README-STORYBOOK.md, AGENTS.md):
| Layer | Tool | Files | Command |
|---|---|---|---|
| Unit and route tests | Vitest, jsdom, Testing Library, MSW | *.test.ts(x) next to source |
pnpm test |
| Component stories | Storybook: snapshot (Vitest), interaction and a11y (Playwright/Chromium) | <component>/stories/*.stories.tsx |
pnpm storybook:test --type=... |
| End to end | CodeceptJS + Playwright | e2e/ |
pnpm e2e |
Prefer the cheapest layer that proves the behavior: pure logic and loaders in Vitest, rendered states and interactions in stories, cross-page shopper flows in e2e.
Commands
pnpm test # all unit tests (vitest run); does NOT collect coverage
pnpm test src/components/footer # one file or directory
pnpm test:watch # watch mode
pnpm test --coverage # coverage report (thresholds enforced)
pnpm test --ui # Vitest UI
pnpm storybook # dev server on :6006
pnpm exec playwright install chromium # once, for interaction/a11y runs
pnpm storybook:test --type=snapshot # add --update to rewrite snapshots
pnpm storybook:test --type=interaction # play() functions in real Chromium
pnpm storybook:test --type=a11y # axe checks
pnpm storybook:test --type=snapshot --stories=footer # narrow to matching story paths
Add --static (optionally --reuse-build after pnpm storybook:build) to run interaction or a11y against a static build. --coverage with snapshot generates story tests and reports story coverage.
Coverage thresholds live inline in vitest.config.ts (thresholds), and src/components/ui/**, stories, snapshot fixtures and __mocks__ are excluded from coverage. Do not chase 100%.
Unit test
import { render, screen } from '@testing-library/react';
import { describe, expect, it } from 'vitest';
import { AllProvidersWrapper } from '@/test-utils/context-provider';
import MyThing from './index';
describe('MyThing', () => {
it('renders the label', () => {
render(<MyThing label="Hello" />, { wrapper: AllProvidersWrapper });
expect(screen.getByText('Hello')).toBeInTheDocument();
});
});
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · -33 lines · +145 tokens per session d3fdbb661cdb
- 1mo ago First seen · 185 lines · 63 tokens per session scan A bb6a9519253f
sfnext-testing is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. It adds 208 tokens to every session and 2,089 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
react-test-engineer
Expert guidance for testing React applications using React Testing Library and Vitest. Focuses on user-centric testing, accessibility, and best practices for unit and integration tests to ensure robust and maintainable code.
react-testing
Testing Library for React 19 - render, screen, userEvent, waitFor, Suspense. Use when writing tests for React components with Vitest.
vitest
Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring…
caliber-testing
Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says…
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.