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 WaniWani-AI/sdk --skill waniwani-sdkgit clone --depth 1 https://github.com/WaniWani-AI/sdkWrote 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/waniwani-ai/sdk/waniwani-sdk)<a href="https://agentmods.dev/skills/waniwani-ai/sdk/waniwani-sdk"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/waniwani-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/waniwani-ai/sdk/waniwani-sdk"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/waniwani-sdk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 104 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 127 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 144 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 145 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00199 | $0.02797 |
| Opus 5 | $0.00100 | $0.01399 |
| Sonnet 5 | $0.00040 | $0.00559 |
| Haiku 4.5 | $0.00020 | $0.00280 |
Grade A, and why
waniwani-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 11d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Waniwani SDK (@waniwani/sdk)
The MCP distribution SDK. Build sales funnels, lead generation, booking, insurance quote, and pricing quote apps on top of your MCP server.
Read the docs before you write code
This file is a map, not a manual. The full, current documentation lives at
docs.waniwani.ai/sdk/introduction and it is the only
source of truth for API shapes, option names, event properties, and version behavior. The SDK is
0.x and moves fast, so anything you remember about it may already be wrong.
Before you answer an API question or write a line of @waniwani/sdk code, fetch the relevant docs
page from the map below. When this file and the docs disagree, the docs win.
If you can fetch only one thing, fetch docs.waniwani.ai/llms.txt: it is the complete page index, always current, and cheap to read.
Where things live in the docs
| You want to... | Fetch |
|---|---|
| Understand what the SDK is and pick a path | /sdk/introduction |
| Get something running end to end | /sdk/quickstart |
| Install the package, pick an entry point | /sdk/configuration/installation, /sdk/reference/entry-points |
| Get a free API key | /sdk/configuration/api-key |
| Learn the flow engine | /sdk/flows/overview, then architecture, state, nodes, edges, interrupts, register |
| Open a flow with an introduction or a GDPR notice | /sdk/flows/intro |
| Plug in Redis / Upstash / Cloudflare KV / DynamoDB | /sdk/flows/kv-store, /sdk/reference/kv-store-api |
| Build a specific funnel | /sdk/guides/funnels, then sales-funnel, lead-generation, booking, insurance-quote |
| See a full worked example | /sdk/guides/pet-insurance |
| Deploy, or self-host with no API key | /sdk/deployment/overview, /sdk/deployment/self-hosting |
| Wrap an existing MCP server, set env vars | /sdk/configuration/wrap-server, /sdk/configuration/environment-variables |
| Track events and build a revenue funnel | /sdk/tracking/overview, events, identify, sessions |
| Know where each event belongs in a flow | /sdk/tracking/instrumentation |
| Check a typed event payload | /sdk/reference/event-schema |
| Add knowledge-base search | /sdk/knowledge-base/overview |
| Embed the chat widget | /sdk/chat/embed (script tag), /sdk/chat/react |
| Read the exact tool contract a flow compiles to | /sdk/reference/flow-tool-contract |
| Tunnel a dev server for remote testing | /sdk/guides/tunnel |
| Use the CLI | /sdk/cli/overview |
| Upgrade the SDK, or fix a build that broke after a bump | /sdk/changelog |
What ships with it
3 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.
- 11d ago First seen · 163 lines · 199 tokens per session scan A 50516c101e1c
waniwani-sdk is a skill published in the GitHub repository WaniWani-AI/sdk (17 stars, last pushed 4d ago), licensed MIT. It adds 199 tokens to every session and 2,797 once invoked, about $0.0010 per session on Opus 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-30.
Other skills, from other repositories
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…