setup-example-sdk

setup-example-sdk is a skill for Claude Code, Codex from scalvert/docusaurus-plugin-mcp-server. It costs 39 tokens per session (701 once invoked), scanned A, original, MIT.

A setup guide for installing the Example SDK, a software package for Node.js projects, and connecting it with an API key. It checks each step before continuing.

In plain words
What is it for?
Installing the package, checking the Node.js version and project files, configuring the API key, and confirming that the SDK works.
Why use it?
It reduces setup mistakes and stops when a required check fails. It also keeps secret keys out of chat messages.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Installing the package, checking the Node.js version and project files, configuring the API key, and confirming that the SDK works.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/scalvert/docusaurus-plugin-mcp-server/compiled
Install

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.

Any agent
npx skills add scalvert/docusaurus-plugin-mcp-server --skill compiled
Clone the repo
git clone --depth 1 https://github.com/scalvert/docusaurus-plugin-mcp-server

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setup-example-sdk

README.md
[![agentmods](https://agentmods.dev/badge/skills/scalvert/docusaurus-plugin-mcp-server/compiled/github.svg)](https://agentmods.dev/skills/scalvert/docusaurus-plugin-mcp-server/compiled)
Your own site
<a href="https://agentmods.dev/skills/scalvert/docusaurus-plugin-mcp-server/compiled"><img src="https://agentmods.dev/badge/skills/scalvert/docusaurus-plugin-mcp-server/compiled/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.

agentmods 80×15 button for setup-example-sdk

Your own site · 80×15
<a href="https://agentmods.dev/skills/scalvert/docusaurus-plugin-mcp-server/compiled"><img src="https://agentmods.dev/badge/skills/scalvert/docusaurus-plugin-mcp-server/compiled.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 701 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00701
Opus 5.5 $0.00016 $0.00280
Sonnet 5.5 $0.00008 $0.00140
Haiku 4.5 $0.00004 $0.00070

Measured 7d ago against content hash 1b3bc57bc6b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-example-sdk 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 7d 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.

videos/projects/agent-guides/capture/compiled-SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Installation

Done when

node -e "import('@example/sdk').then((m) => console.log(new m.Client({ apiKey: process.env.EXAMPLE_API_KEY }).version))" prints a version number.

Before you start

  • Node.js 18 or higher. Check: node --version.
  • A project with a package.json. Check: ls package.json.

How to use this guide

  • Do the steps in order. Run them yourself, or walk the user through them one at a time if they'd rather do it themselves or you can't run them.
  • After each step, run its check. Don't move on until it passes.
  • If a check fails, look for the matching symptom under Troubleshooting. If none matches, stop and tell the user what you saw.
  • A step marked Needs the user needs a person. Tell the user what to do and wait for them to confirm it's done.
  • Ask the user before running a step marked Confirm first.
  • Don't ask the user to paste passwords, tokens, or keys into the chat. When a step needs one, tell the user where to put it.

Steps

1. Installing the SDK {#install}

Install the package using npm:

npm install @example/sdk

Check: npm ls @example/sdk lists the package.

If the check fails: see Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@example/sdk'.

2. Environment Variables {#api-key}

Needs the user.

We recommend storing your API key in an environment variable:

export EXAMPLE_API_KEY=your-api-key

The user creates the key and sets the variable themselves. Never ask them to paste the key into the chat. If they only want to try the SDK, tell them to create a test key: live keys reach production data.

Check: node -e "console.log(Boolean(process.env.EXAMPLE_API_KEY))" prints true.

If the check fails: see Troubleshooting.

3. Verifying Installation {#verify}

After installation, verify it works by importing the SDK:

import { Client } from '@example/sdk';

const client = new Client({
  apiKey: process.env.EXAMPLE_API_KEY,
});

console.log('SDK version:', client.version);

Read the full file on GitHub · 86 lines

Changes

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.

  1. 7d ago First seen · 86 lines · 39 tokens per session scan A 1b3bc57bc6b4

Subscribe to this mod's changes

setup-example-sdk is a skill published in the GitHub repository scalvert/docusaurus-plugin-mcp-server (35 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 701 once invoked, about $0.0002 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-10-31.

Related

setup-example-sdk compared with skills from other repositories

setup-example-sdk next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
setup-example-sdkscalvert/docusaurus-plugin-mcp-serverSkill355d agoMITA39Claude Code, Codex
stripe-projectse2b-dev/E2BSkill15kyesterdayApache-2.0A51Claude Code, Codex
nestjs-expertJeffallan/claude-skillsSkill12k7d agoMITA107Claude Code
chat-sdkvercel-labs/open-agentsSkill5.9k2mo agoMITA191Claude Code, Codex
nestjsericrisco/rsc-harnessSkill5032d agoMITA81Claude Code, Codex
azure-web-pubsub-tsbenjaminasterA/antigravity-awesome-skillsSkill461yesterdayMITA51Claude Code, Codex
better-authsecondsky/claude-skillsSkill2456d agoMITA53Claude Code