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/lukasrepublic/agentic-foundry/nextjs-ssr-patternsnpx skills add lukasrepublic/agentic-foundry --skill nextjs-ssr-patternsgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/nextjs-ssr-patterns)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/nextjs-ssr-patterns"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/nextjs-ssr-patterns.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.00000 | $0.01866 |
| Opus 5 | $0.00000 | $0.00933 |
| Sonnet 5 | $0.00000 | $0.00373 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
nextjs-ssr-patterns 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 5d 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.
- Static: `fetch(url, { cache: 'force-cache' })` or no fetch (build-time data). How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to trigger
- Implementing a spec that names a Next.js web change.
- Deciding between SSR, ISR, SSG, or static page for a new route and its SEO/caching implications.
- Authoring a route handler (
route.ts) or a server/client component. - Metadata API work (
generateMetadata,metadataexport) for SEO. - Sitemap or robots.txt authoring;
next/imageor image-optimization configuration. - Next.js version-bump impact assessment on App Router behavior.
Procedure
-
Determine page type from the spec's requirements: static (no dynamic data at render time), ISR (revalidate on schedule), SSR (dynamic per-request), or dynamic segment (generateStaticParams + fallback). Default: ISR with
revalidateset explicitly. -
Place the file under
app/<route>/page.tsxin the web package per Next.js App Router file-system routing. Route groups use(group-name)/prefix. Parallel routes use@slotprefix. Layout segments uselayout.tsx. Follow the existing folder structure in the package'sapp/directory before introducing new patterns. -
Decide server-component-default vs. client component: default to server component (no directive). Add
'use client'only when the component uses browser-only APIs, React state (useState,useReducer), or event listeners. Push the'use client'boundary as low in the tree as possible — never at the page level if only a leaf needs interactivity. -
Data-fetching pattern:
- Static:
fetch(url, { cache: 'force-cache' })or no fetch (build-time data). - ISR:
fetch(url, { next: { revalidate: N } })where N is seconds. - SSR (per-request dynamic):
fetch(url, { cache: 'no-store' })ornoStore()import. - Never use
getServerSidePropsorgetStaticProps(Pages Router idioms — App Router rejects these).
- Static:
-
Metadata API: for static routes export
const metadata: Metadata = { title, description, openGraph }. For dynamic routes implementexport async function generateMetadata({ params }): Promise<Metadata>. Every public-facing page MUST declare metadata; missing metadata is a build warning and an SEO failure.
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.
- 5d ago First seen · 87 lines · 0 tokens per session scan A c552543b3509
nextjs-ssr-patterns is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,866 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
react-forge
Generate production-ready React components with React Query, design tokens, and enterprise standards.
migrate
Code migration assistant — upgrade frameworks, convert languages, modernize patterns.
frontend-standards
MVVM architecture standards for React/TypeScript frontends with TanStack ecosystem, TailwindCSS, and Shadcn UI.
frontend-scaffolding
Scaffolds React/TypeScript frontend components with MVVM architecture.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…