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 andresquirogadev/skillsense --skill nextjsgit clone --depth 1 https://github.com/andresquirogadev/skillsenseWrote 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/andresquirogadev/skillsense/nextjs)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/nextjs"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/nextjs/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/andresquirogadev/skillsense/nextjs"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/nextjs.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00721 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
nextjs scanned grade A 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Cache with `fetch(url, { next: { revalidate: 60 } })` or `{ cache: 'no-store' }` for dynamic data. How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Skill
You are working on a Next.js project. Apply these conventions and best practices.
App Router (Next.js 13+)
- Use the
app/directory with the App Router by default. Avoidpages/for new code. - Server Components are the default. Add
"use client"only when you need browser APIs, event handlers, or React hooks. - Colocate
page.tsx,layout.tsx,loading.tsx,error.tsx, andnot-found.tsxin route segments. - Use
generateMetadata()for dynamic SEO metadata; use themetadataexport for static metadata. - Prefer
import { notFound } from 'next/navigation'over manual 404 handling.
Data Fetching
- Fetch data directly in Server Components with
async/await— nouseEffectfor server data. - Use Route Handlers (
app/api/route.ts) instead ofpages/api/for API endpoints. - Cache with
fetch(url, { next: { revalidate: 60 } })or{ cache: 'no-store' }for dynamic data. - Use
unstable_cachefromnext/cachefor caching non-fetch async operations. - Call
revalidatePath()orrevalidateTag()in Server Actions after mutations.
Server Actions
- Mark async functions with
'use server'at the top of the file or at function level. - Validate all Server Action inputs with Zod before processing.
- Return
{ error: string }on failure and{ success: true, data: … }on success — never throw. - Use
useFormState/useActionState(React 19) in Client Components to display Server Action results.
Routing & Navigation
- Use
<Link href="…">fromnext/linkfor client-side navigation — never<a>for internal routes. - Use
useRouter()fromnext/navigation(notnext/router) in Client Components. - Use
redirect()fromnext/navigationin Server Components and Server Actions. - Dynamic segments:
[slug]for single,[...slug]for catch-all,[[...slug]]for optional.
Images & Fonts
- Always use
<Image>fromnext/image— never bare<img>for content images. - Load fonts with
next/font/googleornext/font/local; assign toclassNameon<html>.
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.
- 9d ago First seen · 57 lines · 0 tokens per session scan A 01cd34464fd5
nextjs is a skill published in the GitHub repository andresquirogadev/skillsense (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 721 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
expo-config-plugin
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…
expo-router
File-based routing with Expo Router, dynamic routes, layout hierarchy, deep linking, and navigation patterns. Triggers on expo-router, file-based routing, app dizini, layout.tsx, [id].tsx, deep linking, expo-linking, tab navigation, stack navigation, drawer, prefetch, parallel routes, redirects, navigation, useRouter…
ph-frontend
(PH) Use only for an explicitly requested scoped UI change with existing design constraints.
ph-visual-qa
(PH) Use only when the user explicitly requests visual verification and a compatible host can render the UI.
frontend-development
Build robust frontend systems with React, Next.js, and TypeScript. Use when implementing components, hooks, data fetching, state management, or optimizing frontend performance.
open-slide-best-practices
Best practices for authoring presentations with open-slide, the React slide framework with a fixed 1920×1080 canvas, with full Hebrew and RTL support. Covers the slides/[id]/index.tsx file contract, type scale, DesignSystem tokens, themes/ system, @slide-comment inspector markers, current.json deictic resolution…