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 agentmods add agents/amadeusitgroup/otter/sdk-setupgit clone --depth 1 https://github.com/AmadeusITGroup/otterWhat 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 | $0.00105 | $0.00880 |
| Opus 5 | $0.00053 | $0.00440 |
| Sonnet 5 | $0.00021 | $0.00176 |
| Haiku 4.5 | $0.00011 | $0.00088 |
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 2d 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 — 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/coreor@ama-sdk/client-*inpackage.jsondependencies- If found → SDK already created, guide to
use-sdkorsdk-pluginsskills
- If found → SDK already created, guide to
-
Check for existing workspace: Look for
angular.jsonornx.json- If found → monorepo context, use
create-sdkskill (Step A) - If not found → standalone context, use
create-sdkskill (Step B)
- If found → monorepo context, use
-
Check for OpenAPI spec: Look for
.yaml,.yml, or.jsonfiles that containopenapi:orswagger: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-sdkskill - Add plugins/auth → delegate to
sdk-pluginsskill
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-sdkskill "Monorepo Workflow" section - No workspace → follow
create-sdkskill "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-fetchwithApiFetchClient - Angular app →
@ama-sdk/client-angularwithApiAngularClient - Tracking / fire-and-forget →
@ama-sdk/client-beaconwithApiBeaconClient
Guide through client installation and configuration using use-sdk skill patterns.
Phase 5: Plugins (Optional)
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.
- 2d ago First seen · 81 lines · 105 tokens per session scan A 70f7f6915b8c
sdk-setup is an agent published in the GitHub repository AmadeusITGroup/otter (57 stars, last pushed 5d ago), licensed BSD-3-Clause. It adds 105 tokens to every session and 880 once invoked, about $0.0005 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 agents, from other repositories
docgen
The OpenAI-backed JSDoc generation CLI and its review-copy workflow.
angular-implementor
Implements Angular / TypeScript fixes and features in compliance with all materialized angular rules and pilot-angular skills. Takes an angular-reviewer finding (rule/skill ID + file:line) or a feature request, applies minimal targeted edits, verifies with tsc/ng build, and hands back a summary formatted for re-review…
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
automation-components
Automation devices, valves, lines, tanks, badges.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.