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 Mindrally/skills --skill optimized-nextjs-typescriptgit clone --depth 1 https://github.com/Mindrally/skillsWrote 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/mindrally/skills/optimized-nextjs-typescript)<a href="https://agentmods.dev/skills/mindrally/skills/optimized-nextjs-typescript"><img src="https://agentmods.dev/badge/skills/mindrally/skills/optimized-nextjs-typescript/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/mindrally/skills/optimized-nextjs-typescript"><img src="https://agentmods.dev/badge/skills/mindrally/skills/optimized-nextjs-typescript.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00029 | $0.00395 |
| Opus 5.5 | $0.00012 | $0.00158 |
| Sonnet 5.5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
optimized-nextjs-typescript 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 8d 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.
What it actually says
Optimized Next.js TypeScript Best Practices
You are an expert in creating highly optimized and maintainable Next.js solutions adhering to best practices in performance, security, and clean architecture principles.
Code Style and Structure
- Write concise, technical TypeScript with functional, declarative patterns
- Avoid classes; favor composition and modularization
- Use descriptive variable names with auxiliary verbs (e.g.,
isLoading,hasError) - Organize files with exported components, subcomponents, helpers, static content, and types
- Use lowercase with dashes for directory naming conventions
Optimization Best Practices
- Minimize
'use client',useEffect, andsetState; prioritize React Server Components - Implement dynamic imports for code splitting
- Use mobile-first responsive design
- Optimize images with WebP format, size data, and lazy loading
Error Handling and Validation
- Prioritize comprehensive error handling and edge cases
- Use early returns and guard clauses for preconditions
- Implement custom error types for consistency
- Validate user input rigorously
UI and Styling
- Leverage modern frameworks: Tailwind CSS, Shadcn UI, Radix UI
- Maintain consistent, responsive design patterns
State and Data Management
- Use Zustand or TanStack React Query for state and data fetching
- Implement Zod for schema validation
Security and Performance
- Apply proper error handling and input validation
- Follow performance optimization techniques for load times and rendering
Testing and Documentation
- Write Jest and React Testing Library unit tests
- Include JSDoc comments for IDE intellisense
- Document complex logic clearly
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.
- 8d ago Changed · +3 lines 1ad00f7be1ec
- 1mo ago First seen · 52 lines · 29 tokens per session scan A b9b9360eebf6
optimized-nextjs-typescript is a skill published in the GitHub repository Mindrally/skills (277 stars, last pushed 8d ago), licensed Apache-2.0. It adds 29 tokens to every session and 395 once invoked, about $0.0001 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-component-generator
Generate React components with TypeScript, proper props, hooks, and accessibility. Use when creating new React components, UI elements, or refactoring existing components.
aio-xstate
Implement XState v5 state machines with strict patterns — setup().createMachine(), actors, and TypeScript typing. Use when working with finite state machines (FSM), statecharts, state diagrams, or the actor model in TypeScript. Covers @xstate/react integration (useMachine, useActor, useSelector), parallel states…
electron-dev
Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.
coding-standards
A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
typescript-dev
Full-stack TypeScript with Vite 8, React 19, Tailwind v4, shadcn/ui, Biome, Vitest, and Hono 4. Use when setting up or working in a TypeScript project - components, styling, build and HMR, tests, lint/CI, or a Hono API with type-safe RPC.