Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentnpx agentmods add skills/sdcorejs/sdcorejs-agent/sdcorejs-nextjsWrote 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/sdcorejs/sdcorejs-agent/sdcorejs-nextjs)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-nextjs"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-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/sdcorejs/sdcorejs-agent/sdcorejs-nextjs"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-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.00097 | $0.04326 |
| Opus 5.5 | $0.00039 | $0.01730 |
| Sonnet 5.5 | $0.00019 | $0.00865 |
| Haiku 4.5 | $0.00010 | $0.00433 |
Grade A, and why
sdcorejs-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 16d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path resolution: Resolve ../../_refs/... relative to this SKILL.md. Resolve another SDCoreJS skill by opening the sibling folder ../<skill-name>/SKILL.md.
Build Website — Write Code Orchestrator
For unresolved visual decisions, apply ../../_refs/sdlc/visual-offer-policy.md;
forward requirement_context.visual_companion through context.pass
(portable state_delta.visual_companion) to the owning workflow.
Shared Protocols
Read ../../_refs/shared/runtime-protocols.md and ../../_refs/shared/artifact-lifecycle.md; merge producer artifact_context through the finishing tail.
Purpose
Single entry point for generating approved Next.js website code. This skill is the
dispatch layer between an approved plan from sdcorejs-execute-plan and the
focused REFERENCE PACKS that hold the per-concern generation rules. It does NOT
inline those rules — it reads the right pack on demand. The ten packs under
../../_refs/nextjs/build-website/write-code/ were standalone sub-skills before they
were consolidated here so the track exposes one orchestrator instead of eleven.
When invoked
- After
sdcorejs-execute-plandispatches an approved Next.js plan - After
sdcorejs-explore (recovery mode)and the user explicitly resumes the same approved plan
Do NOT invoke if:
- No plan exists or plan is unapproved -> go back to
sdcorejs-brainstorming/sdcorejs-spec/sdcorejs-plan - Scope changed since plan was approved -> re-plan with
sdcorejs-plan - The user wants to AUDIT an existing site (not generate) →
sdcorejs-review
Step 0 — Read-oriented project context
Before reading the plan or dispatching, assemble read-only project_context.
Use valid summary sections when available. For an existing site with a missing,
legacy, unknown, or stale summary, continue with targeted reads and use a scoped
code map only for unresolved cross-component relationships. Do not refresh
merely because summary is absent. A brand-new approved init-site may create
summary v2 after scaffolding; an architecture-level refresh belongs only to the
sequential workflow or integration owner.
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.
- 16d ago Changed · +2 lines b84b9300b6c0
- 1mo ago Changed · +9 lines 45d18cfab52b
- 2mo ago First seen · 252 lines · 97 tokens per session scan A 569a05309078
sdcorejs-nextjs is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 97 tokens to every session and 4,326 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…