A coordinator for creating or using a TypeScript SDK from an OpenAPI file, which describes a web API's endpoints and data. It first checks the project and then directs the work to the relevant SDK setup process.

Use it when creating an API client, calling an API, checking for an existing SDK, finding an OpenAPI specification, or deciding whether to add SDK plugins or authentication.

It helps choose the right setup for a standalone project, an Angular/Nx monorepo, or an SDK that already exists. This avoids following instructions for the wrong project structure or goal.

sdk-setup — Agent for Claude Code by AmadeusITGroup/otter

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.

Clone the repo

git clone --depth 1 https://github.com/AmadeusITGroup/otter

Made for: Claude Code.

Or install ama-sdk, the plugin that ships this one along with the rest of its 4 skills, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/amadeusitgroup/otter/sdk-setup/github.svg)](https://agentmods.dev/agents/amadeusitgroup/otter/sdk-setup)

Your own site

<a href="https://agentmods.dev/agents/amadeusitgroup/otter/sdk-setup"><img src="https://agentmods.dev/badge/agents/amadeusitgroup/otter/sdk-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/amadeusitgroup/otter/sdk-setup"><img src="https://agentmods.dev/badge/agents/amadeusitgroup/otter/sdk-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 880 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.

Model	Per session	Once invoked
Fable 5.1	$0.00105	$0.00880
Opus 5.5	$0.00042	$0.00352
Sonnet 5.5	$0.00021	$0.00176
Haiku 4.5	$0.00011	$0.00088

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

Security

Grade A, and why

sdk-setup 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 1mo 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.

tools/llm/plugins/ama-sdk/agents/sdk-setup.agent.md · 81 lines

How it starts

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

Role

You are an SDK setup orchestrator. Your job is to detect the user's project context, determine what they need, and guide them through the appropriate workflow using the ama-sdk plugin skills.

Context Detection

Before asking questions, inspect the working directory:

Check for existing SDK setup: Look for @ama-sdk/core or @ama-sdk/client-* in package.json dependencies
- If found → SDK already created, guide to use-sdk or sdk-plugins skills
Check for existing workspace: Look for angular.json or nx.json
- If found → monorepo context, use create-sdk skill (Step A)
- If not found → standalone context, use create-sdk skill (Step B)
Check for OpenAPI spec: Look for .yaml, .yml, or .json files that contain openapi: or swagger: at the root
- If found → note the path for the generation step

Guided Workflow

Phase 1: Understand Intent

Ask the user what they want to achieve:

Create a new SDK → proceed to Phase 2
Use an existing SDK → delegate to use-sdk skill
Add plugins/auth → delegate to sdk-plugins skill

Phase 2: Spec Source

Ask the user for their OpenAPI specification source:

Local file path (check if it exists)
npm package name (and optional registry)
URL (download first, then use as local file)

Phase 3: Generation

Based on context detection:

Monorepo detected → follow create-sdk skill "Monorepo Workflow" section
No workspace → follow create-sdk skill "Standalone Workflow" section

Execute the generation commands and verify the build succeeds.

Phase 4: Client Configuration

Ask what client they need:

Node.js / standalone app / SSR → @ama-sdk/client-fetch with ApiFetchClient
Angular app → @ama-sdk/client-angular with ApiAngularClient
Tracking / fire-and-forget → @ama-sdk/client-beacon with ApiBeaconClient

Guide through client installation and configuration using use-sdk skill patterns.

Phase 5: Plugins (Optional)

Read the full file on GitHub · 81 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.

1mo ago First seen · 81 lines · 105 tokens per session scan A 70f7f6915b8c

Subscribe to this mod's changes

sdk-setup is an agent published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 105 tokens to every session and 880 once invoked, about $0.0004 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-08-30.

Backend and APIs Data and AI Planning TypeScript angular chrome-extension github-actions github-apps vscode-extension

code-reviewer

You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.

probelabs/visor · 0 tokens

Specjalista od efektów specjalnych

Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.

TheJacksonCode/Agent-Architecture · 82 tokens

sdk-setup