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/darellchua2/opencode-config-template/nextjs-complete-setupnpx skills add darellchua2/opencode-config-template --skill nextjs-complete-setupgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWhat 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.00032 | $0.05301 |
| Opus 5 | $0.00016 | $0.02651 |
| Sonnet 5 | $0.00006 | $0.01060 |
| Haiku 4.5 | $0.00003 | $0.00530 |
Grade A, and why
nextjs-complete-setup 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.
How it starts
The opening of the file, as written. The whole thing — 860 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this workflow does
- Creates a fully standardized Next.js 16 application with shadcn, Tailwind v4, and src directory
- Establishes Tekk-prefixed component architecture with named exports
- Enables React Compiler for optimized performance
- Applies comprehensive TSDoc documentation to all generated TypeScript functions
- Ensures all components and functions follow TSDoc industry standards
- Configures TSDoc validation and linting rules
- Sets up proper TypeScript strict mode and type checking
- Implements npx zero-install experience throughout
When to use
Use this workflow when:
- Starting a new Next.js demo application from scratch
- Need both project structure and documentation standards in one step
- Want to ensure TSDoc compliance from the beginning
- Creating maintainable, well-documented component architecture
- Setting up projects with comprehensive quality standards
- Need automated TSDoc validation in the development workflow
Common signals:
- New Next.js project initialization required
- Both project setup and documentation needed simultaneously
- Want to establish TSDoc standards early in project lifecycle
- Need production-ready Next.js architecture with full documentation
Workflow Overview
This workflow combines two skills in sequence:
-
Phase 1: Project Setup (
nextjs-standard-setup)- Initialize Next.js 16 with TypeScript and Tailwind v4
- Configure shadcn component library
- Create src/ directory structure with path aliases
- Set up Tekk-prefixed component architecture
- Enable React Compiler
- Configure TypeScript strict mode
- Set up ESLint and Prettier
-
Phase 2: Documentation (
nextjs-tsdoc-documentor)- Apply TSDoc to all generated components and functions
- Configure TSDoc validation in ESLint
- Ensure parameter and return type documentation
- Set up TSDoc best practices
- Validate TSDoc completeness
Prerequisites
- Node.js 24+ installed
- npm package manager
- Git repository initialized (optional but recommended)
- Terminal/shell access
- Internet connection for package installation
- Familiarity with Next.js and TypeScript concepts
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 · 860 lines · 32 tokens per session scan A 8c61cba279f1
nextjs-complete-setup is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 5,301 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
custom-features
Author a TanStack Table v9 feature plugin across every FeatureMap and API installation surface: state, options, column definitions, table, column, row, cell, header, row-model functions/caches, defaults, prototypes, and table/row/column instance data lifecycles. Load for initTableInstanceData, resetTableInstanceData…
effect-and-errors
Composing Effect programs, domain errors, HttpError, repository error types, or error propagation at HTTP boundaries.
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
typescript-magician
Designs complex generic types, refactors any types to strict alternatives, creates type guards and utility types, and resolves TypeScript compiler errors. Use when the user asks about TypeScript (TS) types, generics, type inference, type guards, removing any types, strict typing, type errors, infer, extends…