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 laguagu/claude-code-nextjs-skills --skill ai-sdkgit clone --depth 1 https://github.com/laguagu/claude-code-nextjs-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/laguagu/claude-code-nextjs-skills/ai-sdk)<a href="https://agentmods.dev/skills/laguagu/claude-code-nextjs-skills/ai-sdk"><img src="https://agentmods.dev/badge/skills/laguagu/claude-code-nextjs-skills/ai-sdk/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/laguagu/claude-code-nextjs-skills/ai-sdk"><img src="https://agentmods.dev/badge/skills/laguagu/claude-code-nextjs-skills/ai-sdk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00122 | $0.01657 |
| Opus 5 | $0.00061 | $0.00829 |
| Sonnet 5 | $0.00024 | $0.00331 |
| Haiku 4.5 | $0.00012 | $0.00166 |
Grade A, and why
ai-sdk 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 12d 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.
7. **Always fetch current model IDs** - Never use model IDs from memory. A public catalog of current IDs across providers is available at `https://ai-gateway.vercel.sh/v1/models` — useful purely for discovery, not a reco How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
Before searching docs, check the installed major version in package.json,
lockfiles, or node_modules/ai/package.json.
- AI SDK 7 implementation or migration work -> use
ai-sdk-7. - AI SDK 6 implementation work -> use
ai-sdk-6. - Unknown or mixed versions -> continue with this skill until the version is
clear. If starting fresh or no version is pinned, assume the current line
(AI SDK 7) and use
ai-sdk-7.
Before searching docs, check if node_modules/ai/docs/ exists. If not, install
only the ai package using the project's package manager (e.g., bun add ai).
Do not install other packages at this stage. Provider packages (e.g., @ai-sdk/openai) and client packages (e.g., @ai-sdk/react) should be installed later when needed based on user requirements.
Monorepo path note
In Bun / pnpm / Yarn workspace monorepos, dependencies are usually not hoisted to the repo root — they live inside each app's node_modules/. If node_modules/ai/docs/ doesn't exist at the working directory, check workspace locations before assuming docs are missing:
apps/*/node_modules/ai/docs/(e.g.apps/web/node_modules/ai/docs/)packages/*/node_modules/ai/docs/
Glob from the repo root: apps/*/node_modules/ai/docs/ or **/node_modules/ai/docs/. Substitute the resolved path everywhere this skill says node_modules/ai/docs/ or node_modules/ai/src/. The same applies to provider docs at node_modules/@ai-sdk/<provider>/docs/.
Critical: Do Not Trust Internal Knowledge
Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.
When working with the AI SDK:
- Ensure
aipackage is installed (see Prerequisites) - Identify the installed major version and use
ai-sdk-7orai-sdk-6for deep version-specific work - Search
node_modules/ai/docs/andnode_modules/ai/src/for current APIs - If not found locally, search ai-sdk.dev documentation (instructions below)
- Never rely on memory - always verify against source code or docs
useChathas changed significantly - check Common Errors before writing client code- Always fetch current model IDs - Never use model IDs from memory. A public catalog of current IDs across providers is available at
https://ai-gateway.vercel.sh/v1/models— useful purely for discovery, not a recommendation to use Gateway as a runtime provider. Example:curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("anthropic/")) | .id] | reverse | .[]'(swapanthropic/foropenai/,google/, etc.). Pick the model family/tier by capability, cost, and latency requirements; within the chosen family, use the latest version from the catalog (e.g. preferclaude-sonnet-5over an olderclaude-sonnet-4-x) — version number alone is not a selection criterion across families. - Run typecheck after changes to ensure code is correct
- Be minimal - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 118 lines · 122 tokens per session scan A f525cc1700bf
ai-sdk is a skill published in the GitHub repository laguagu/claude-code-nextjs-skills (62 stars, last pushed 9d ago), licensed MIT. It adds 122 tokens to every session and 1,657 once invoked, about $0.0006 per session on Opus 5. 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-30.
Other skills, from other repositories
adhx
Fetch X/Twitter posts as clean LLM-friendly JSON via the ADHX API. Converts any x.com, twitter.com, or adhx.com link into structured data with full article content, author info, and engagement metrics. Use when a user shares an X/Twitter link (x.com, twitter.com, adhx.com) and wants to read, analyze, or summarize the…
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
gemini-api-agent-platform
Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.