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 skills/amadeusitgroup/otter/use-sdknpx skills add AmadeusITGroup/otter --skill use-sdkgit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/use-sdk)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/use-sdk"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/use-sdk.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 | $0.00048 | $0.01811 |
| Opus 5 | $0.00024 | $0.00905 |
| Sonnet 5 | $0.00010 | $0.00362 |
| Haiku 4.5 | $0.00005 | $0.00181 |
Grade A, and why
use-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 5d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use SDK
Install a TypeScript SDK, generated with @ama-sdk/schematics, configure an API client, and make API calls.
Choosing a Client
| Client | Package | Best For |
|---|---|---|
| ApiFetchClient | @ama-sdk/client-fetch |
Node.js, browsers, standalone apps, SSR, Angular apps with ApiManager |
| ApiAngularClient | @ama-sdk/client-angular |
Angular apps needing HttpClient (interceptors, SSR transfer state) |
| ApiBeaconClient | @ama-sdk/client-beacon |
Fire-and-forget tracking/analytics calls |
In Angular apps, prefer ApiFetchClient with ApiManager (see below) unless you specifically need Angular's HttpClient features (interceptors, transfer state).
Setup: ApiFetchClient (Standalone / Node.js / Browser)
Install
# @my-org/my-sdk is a placeholder for the generated SDK package name
npm install @ama-sdk/client-fetch @ama-sdk/core @my-org/my-sdk
Configure
import { ApiFetchClient } from '@ama-sdk/client-fetch';
import { PetApi } from '@my-org/my-sdk';
const client = new ApiFetchClient({
basePath: 'https://api.example.com/v1',
requestPlugins: [],
fetchPlugins: []
});
const petApi = new PetApi(client);
Constructor Options
For the full list of options, read the source interfaces:
- ApiFetchClient options: https://github.com/AmadeusITGroup/otter/blob/main/packages/@ama-sdk/client-fetch/src/api-fetch-client.ts (see
BaseApiFetchClientOptionsandBaseApiFetchClientConstructor) - Base options (shared by all clients): https://github.com/AmadeusITGroup/otter/blob/main/packages/@ama-sdk/core/src/fwk/core/base-api-constructor.ts (see
BaseApiClientOptions)
Setup: ApiAngularClient (Angular Apps)
Install
ng add @ama-sdk/client-angular
npm install @my-org/my-sdk
Configure
import { inject } from '@angular/core';
import { HttpClient } from '@angular/common/http';
import { ApiAngularClient } from '@ama-sdk/client-angular';
const client = new ApiAngularClient({
httpClient: inject(HttpClient),
basePath: 'https://api.example.com/v1'
});
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.
- 5d ago First seen · 246 lines · 48 tokens per session scan A 0ef939aae44b
use-sdk is a skill published in the GitHub repository AmadeusITGroup/otter (57 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 48 tokens to every session and 1,811 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-30.
Other skills, from other repositories
typescript-language
Apply modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings.
typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
typescript-best-practices
Write idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic.
angular
Use when building, refactoring, or debugging Angular (v20/21+): standalone components, signals, zoneless change detection, @if/@for/@defer control flow, inject() DI, resource()/httpResource(), RxJS interop, NgRx SignalStore, ng CLI. NOT React (that is react), NOT Next.js (that is nextjs), NOT a TypeScript language…
authoring-typescript
Best practices for TypeScript code including type safety, discriminated unions, type guards, and exhaustive checking. Use this skill whenever the user asks about TypeScript patterns, type safety, type assertions (as any, as unknown), non-null assertions, discriminated unions, exhaustive switch/never patterns, type…
code-quality-analysis
Analyze Angular / Cumulocity Web SDK code for anti-patterns, bugs, and quality issues. Use when reviewing components, services, or modules for code quality, maintainability, performance, and correctness. Covers TypeScript best practices, Angular idioms, C8Y SDK usage patterns, and project-specific conventions.…