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 fiber-ai/fiber-ai-plugin --skill sdk-tsgit clone --depth 1 https://github.com/fiber-ai/fiber-ai-pluginWrote 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/fiber-ai/fiber-ai-plugin/sdk-ts)<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/sdk-ts"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/sdk-ts.svg" alt="Measured on agentmods" 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.00041 | $0.01037 |
| Opus 5 | $0.00020 | $0.00518 |
| Sonnet 5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
sdk-ts 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiber AI TypeScript SDK
Help the user write TypeScript or JavaScript code using the @fiberai/sdk package.
When to Use
- User wants to BUILD an application using Fiber AI (not just query via MCP)
- User says "build", "create app", "write code", "typescript", "javascript", "node"
- User wants a wrapper, integration, data pipeline, or product on top of Fiber APIs
Do Not Use When
- User just wants to search or enrich via chat — use
/fiber:searchor/fiber:enrichinstead - User wants to write Python code — use
/fiber:sdk-pyinstead
Quick Start
import { createClient, companySearch } from "@fiberai/sdk";
const client = createClient({
baseUrl: "https://api.fiber.ai",
});
const result = await companySearch({
client,
body: {
apiKey: process.env.FIBER_API_KEY!,
searchParams: { /* filters */ },
pageSize: 25,
},
});
Key Concepts
- The SDK provides typed functions for every API endpoint
- Each API operationId becomes a named exported function (e.g.,
companySearch,peopleSearch,syncQuickContactReveal) apiKeyis passed in the request body (for POST) or query string (for GET), not as a header- Search filters go inside a
searchParamsobject, not afiltersobject - Pagination uses
cursor, notpage - All functions are async and return typed responses
zodis included for runtime validation schemas
Schema & Type Discovery
Fiber's request/response schemas are large and evolve across versions. The SDK is the best source of truth for field names and types:
- From the installed package: check the exported types in
@fiberai/sdk. Every operation function has fully typed parameters and return values. Use IDE autocomplete or inspectnode_modules/@fiberai/sdkto discover available fields forsearchParams,enrichmentType, etc. - From online docs: per-operation pages at
https://api.fiber.ai/ai-docs/<operationId>.mddescribe every field with examples. Start withhttps://api.fiber.ai/llms.txtfor routing. - From MCP at runtime: call
get_endpoint_details_full("<operationId>")on the Core MCP to get the full current schema. - Open-source examples:
https://github.com/fiber-ai/open-fiberhas working code samples.
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.
- 7d ago First seen · 85 lines · 41 tokens per session scan A c5b786b791ae
sdk-ts is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,037 once invoked, about $0.0002 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-31.
Other skills, from other repositories
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…
nestjs-expert
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…
fastify-best-practices
Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…