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/nth5693/gemini-kit/nextjsnpx skills add nth5693/gemini-kit --skill nextjsgit clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/nextjs)<a href="https://agentmods.dev/skills/nth5693/gemini-kit/nextjs"><img src="https://agentmods.dev/badge/skills/nth5693/gemini-kit/nextjs.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 | $0.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
nextjs 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 3d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Best Practices Skill
Overview
Next.js App Router architecture, Server Components, and modern patterns.
Core Concepts
1. App Router Structure
app/
├── layout.tsx # Root layout
├── page.tsx # Home page
├── loading.tsx # Loading UI
├── error.tsx # Error UI
├── not-found.tsx # 404 page
├── (marketing)/ # Route group
│ ├── about/
│ └── contact/
└── api/
└── route.ts # API route
2. Server vs Client Components
// Server Component (default)
async function UserProfile({ userId }: { userId: string }) {
const user = await getUser(userId); // Direct DB access
return <div>{user.name}</div>;
}
// Client Component
'use client';
import { useState } from 'react';
function Counter() {
const [count, setCount] = useState(0);
return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
}
3. Data Fetching
// Server Component with fetch
async function Posts() {
const posts = await fetch('https://api.example.com/posts', {
next: { revalidate: 3600 } // ISR: revalidate every hour
}).then(res => res.json());
return posts.map(post => <PostCard key={post.id} post={post} />);
}
// Server Actions
'use server';
async function createPost(formData: FormData) {
const title = formData.get('title');
await db.posts.create({ title });
revalidatePath('/posts');
}
4. Metadata & SEO
export const metadata: Metadata = {
title: 'My App',
description: 'App description',
openGraph: {
title: 'My App',
images: ['/og-image.png'],
},
};
// Dynamic metadata
export async function generateMetadata({ params }): Promise<Metadata> {
const post = await getPost(params.id);
return { title: post.title };
}
5. Route Handlers (API)
// app/api/users/route.ts
import { NextResponse } from 'next/server';
export async function GET(request: Request) {
const users = await getUsers();
return NextResponse.json(users);
}
export async function POST(request: Request) {
const body = await request.json();
const user = await createUser(body);
return NextResponse.json(user, { status: 201 });
}
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.
- 3d ago First seen · 102 lines · 0 tokens per session scan A 75eaf948bd5d
nextjs is a skill published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 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-30.
Other skills, from other repositories
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
minimalist-general
Subtraction-first thinking for non-coding tasks: writing, planning, research, summarizing, decision-making, or any request that isn't producing code. Same discipline as the minimalist coding skill — question whether the ask is even needed, reuse what already exists, do the smallest thing that fully answers it …
minimalist
Subtraction-first engineering for any coding task. Use when writing, fixing, refactoring, reviewing, or designing code; when choosing dependencies; or whenever the user asks for minimalist, less code, simplest thing, YAGNI, or complains about bloat. Prefer deletion, existing code, stdlib, and native platform features…
minimalist-audit
Audit a codebase or directory for deletion candidates: dead code, unused dependencies, single-use abstractions, config that never varies, and duplicated helpers. Use when the user says "minimalist audit" or asks what can be deleted from a project.
minimalist-gain
Report what minimalist actually measured in this session or project — LOC avoided, scope rejected, dependencies declined. Use when the user says "minimalist gain", "what did you save", or asks for the savings report.
minimalist-review
Review code, a diff, or a PR strictly for bloat: unrequested abstractions, dead scope, dependency creep, symptom-patching, and drive-by changes. Use when the user says "minimalist review", asks "is this over-engineered?", or wants a leanness review of a change.