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 scalvert/docusaurus-plugin-mcp-server --skill compiledgit clone --depth 1 https://github.com/scalvert/docusaurus-plugin-mcp-serverWrote 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/scalvert/docusaurus-plugin-mcp-server/compiled)<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.
<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>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.00039 | $0.00701 |
| Opus 5.5 | $0.00016 | $0.00280 |
| Sonnet 5.5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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.
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);
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.
- 7d ago First seen · 86 lines · 39 tokens per session scan A 1b3bc57bc6b4
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.
setup-example-sdk compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| setup-example-sdkscalvert/docusaurus-plugin-mcp-server | Skill | 35 | 5d ago | MIT | A | 39 | Claude Code, Codex |
| stripe-projectse2b-dev/E2B | Skill | 15k | yesterday | Apache-2.0 | A | 51 | Claude Code, Codex |
| nestjs-expertJeffallan/claude-skills | Skill | 12k | 7d ago | MIT | A | 107 | Claude Code |
| chat-sdkvercel-labs/open-agents | Skill | 5.9k | 2mo ago | MIT | A | 191 | Claude Code, Codex |
| nestjsericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 81 | Claude Code, Codex |
| azure-web-pubsub-tsbenjaminasterA/antigravity-awesome-skills | Skill | 461 | yesterday | MIT | A | 51 | Claude Code, Codex |
| better-authsecondsky/claude-skills | Skill | 245 | 6d ago | MIT | A | 53 | Claude Code |