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 skills add darellchua2/opencode-config-template --skill nextjs-unit-test-creator-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/nextjs-unit-test-creator-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/nextjs-unit-test-creator-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/nextjs-unit-test-creator-skill.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.1 | $0.00031 | $0.08525 |
| Opus 5 | $0.00015 | $0.04262 |
| Sonnet 5 | $0.00006 | $0.01705 |
| Haiku 4.5 | $0.00003 | $0.00852 |
Grade C, and why
nextjs-unit-test-creator-skill scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
When protocol is enabled, this skill defaults to `Iterations: 10` (sufficient for typical single-pass workflows). Override with `Iterations: N` for specific tasks. Safety blocks: `.env`, `node_modules/`, `rm -rf`, `git p How it starts
The opening of the file, as written. The whole thing — 1,185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I implement a complete Next.js 16 test generation workflow by extending test-generator-framework:
- Analyze Next.js Codebase: Scan Next.js 16 application to identify components, hooks, and utilities using App Router patterns
- Detect Next.js Framework: Identify specific Next.js testing setup (Vitest recommended for Next.js 16, Jest, Playwright) from
package.json - Generate Next.js-16-Specific Scenarios: Create comprehensive test scenarios covering:
- App Router Components: Server components (
page.tsx,layout.tsx,loading.tsx,error.tsx) - Client Components:
"use client"components with hooks and interactions - Server Actions:
asyncserver action functions and mutations - API Routes: App Router API handlers (
app/api/*/route.ts) - Hooks: Custom hooks with React-specific patterns
- Utility Functions: Next.js utilities (routing, data fetching, validation)
- E2E Tests: Next.js routing, page navigation, API routes (if Playwright detected)
- App Router Components: Server components (
- Delegate to Framework: Use
test-generator-frameworkfor core test generation workflow - Ensure Executability: Verify tests run with
npm run test- ALL TESTS MUST PASS - Validate Next.js 16 Patterns: Ensure tests handle Server Components, Suspense, and App Router correctly
Critical Requirement: All generated tests must pass (npm run test) before PR creation. This integrates with nextjs-pr-workflow to enforce test validation.
When to use me
Use this workflow when:
- You need to create unit tests for new Next.js components
- You want to ensure all edge cases and user interactions are covered
- You need tests for utility functions in a Next.js application
- You need E2E tests for Next.js applications (Playwright)
- You prefer a systematic approach to test generation with user confirmation
- You want to ensure tests run correctly with your project's test framework
Framework: This skill extends test-generator-framework for core test generation workflow, adding Next.js-specific functionality.
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.
- 4d ago First seen · 1,185 lines · 31 tokens per session scan C 697e69248004
nextjs-unit-test-creator-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 8,525 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
frontend-testing
Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
angular-testing
Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking…
angular-testing
Testing Angular 18-21: TestBed, component harnesses (@angular/cdk/testing), Karma+Jasmine (default historical) vs Jest (jest-preset-angular, modern), Angular Testing Library (RTL-style). HttpClient mocking via HttpTestingController. NgRx Effects testing. Cypress / Playwright e2e. Use this skill to: Detect runner…
vue-testing
Testing Vue 3 SPAs: Vitest + @vue/test-utils, RTL-style alternatives, Pinia testing via createTestingPinia, composable testing, msw for network mocks, Cypress component testing, Playwright e2e. Use this skill to: Set up Vitest for Vue 3 with jsdom + @vue/test-utils. Pick mount vs shallowMount. Test components by…
react-testing
Testing React SPAs: React Testing Library + Vitest/Jest for components and hooks, msw for network mocks, Playwright/Cypress for e2e. Query priority, user events, async assertions, mocking patterns. Use this skill to: Pick the right runner (Vitest vs Jest) and setup. Write component tests with RTL using accessible…