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/create-sdknpx skills add AmadeusITGroup/otter --skill create-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/create-sdk)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/create-sdk"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/create-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.00047 | $0.01271 |
| Opus 5 | $0.00023 | $0.00635 |
| Sonnet 5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
create-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 4d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SDK
Generate a TypeScript SDK from an OpenAPI specification — standalone or within a monorepo.
Prerequisites
- Node.js (LTS recommended)
- An OpenAPI 3.x or Swagger 2.0 specification file (YAML or JSON)
- For monorepo: an existing Angular/Nx workspace (
angular.jsonornx.json)
Determine Context
Before running commands, check the working directory:
angular.jsonornx.jsonexists → monorepo workflow (Step A)- No workspace file → standalone workflow (Step B)
Step A: Monorepo Workflow
A1. Add @ama-sdk/schematics to the workspace
ng add @ama-sdk/schematics
A2. Scaffold the SDK shell
ng generate @ama-sdk/schematics:typescript-shell --name=my-sdk
This creates a library project (e.g., libs/my-sdk/) with package.json, tsconfig.json, and the source directory structure.
A3. Generate SDK from spec
ng generate @ama-sdk/schematics:typescript-core --spec-path=./path/to/openapi.yaml
Run from inside the SDK library directory, or pass the project name if supported by your workspace.
A4. Generate mocks (optional)
ng generate @ama-sdk/schematics:typescript-mock
A5. Workspace integration
- tsconfig paths: Map the SDK package name in
tsconfig.base.json(e.g.,"@my-org/my-sdk": ["libs/my-sdk/src/index.ts"]) - Build order: If using Nx, the SDK library is buildable and other projects can depend on it
- Importing: Other apps import from the SDK by package name
A6. Regeneration
When the OpenAPI spec changes:
ng generate @ama-sdk/schematics:typescript-core --spec-path=./path/to/updated-spec.yaml
This regenerates src/api/ and src/models/base/ while preserving custom core models.
Step B: Standalone Workflow
B1. Create the SDK project
From a local spec file:
npm create @ama-sdk typescript @scope/my-sdk -- --spec-path ./path/to/openapi.yaml
From an npm package containing the spec:
npm create @ama-sdk typescript @scope/my-sdk -- --spec-package-name @scope/my-spec --spec-package-registry https://registry.example.com
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.
- 4d ago First seen · 157 lines · 47 tokens per session scan A 960f588ad64f
create-sdk is a skill published in the GitHub repository AmadeusITGroup/otter (57 stars, last pushed today), licensed BSD-3-Clause. It adds 47 tokens to every session and 1,271 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
build-page-layout
Build a page layout using fd-dynamic-page or fdp-dynamic-page — collapsing header, subheader, content area, footer, and optional tabs.
adopt-styles
Adopt breaking changes from fundamental-styles into Angular components.
build-form
Build a reactive form with @fundamental-ngx/platform form components, FormGroup wiring, validation, and error states.
build-table
Build a @fundamental-ngx/platform data table with FdpTableDataSource, sorting, filtering, pagination, and row selection.
i18n-manage
Add, rename, or remove i18n translation keys in fundamental-ngx (updates FdLanguage interface, .properties files, and generated types).
setup-project
Set up a new Angular project with @fundamental-ngx installed, themed, and a working first component.