agentmods.dev

otter-migration

otter-migration is an agent for Claude Code from AmadeusITGroup/otter. It costs 112 tokens per session (7,149 once invoked), scanned C, original, BSD-3-Clause.

A migration helper for upgrading Otter and related Angular packages across a monorepo, a code repository containing multiple connected packages.

In plain words
What is it for?
Use it to upgrade @o3r, @ama-mfe, or @ama-sdk packages, update Angular dependencies when needed, and check that the workspace still works.
Why use it?
It organizes the upgrade and handles version alignment, peer-dependency conflicts, and code changes that migration tools would normally apply.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the otter plugin — 11 skills, 3 agents shipped together

not rated 59repo changed 1mo ago C scan 112 tokens original BSD-3-Clause

Good fit Use it to upgrade @o3r, @ama-mfe, or @ama-sdk packages, update Angular dependencies when needed, and check that the workspace still works.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/amadeusitgroup/otter/otter-migration
View source ↗ AmadeusITGroup/otter amadeusitgroup.github.io
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 otter, the plugin that ships this one along with the rest of its 11 skills, 3 agents.

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.

agentmods badge for otter-migration

README.md
[![agentmods](https://agentmods.dev/badge/agents/amadeusitgroup/otter/otter-migration/github.svg)](https://agentmods.dev/agents/amadeusitgroup/otter/otter-migration)
Your own site
<a href="https://agentmods.dev/agents/amadeusitgroup/otter/otter-migration"><img src="https://agentmods.dev/badge/agents/amadeusitgroup/otter/otter-migration/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.

agentmods 80×15 button for otter-migration

Your own site · 80×15
<a href="https://agentmods.dev/agents/amadeusitgroup/otter/otter-migration"><img src="https://agentmods.dev/badge/agents/amadeusitgroup/otter/otter-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00112 $0.07149
Opus 5.5 $0.00045 $0.02860
Sonnet 5.5 $0.00022 $0.01430
Haiku 4.5 $0.00011 $0.00715

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

Security

Grade C, and why

otter-migration scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

find . -name node_modules -type d -prune -exec rm -rf {} +
tools/llm/plugins/otter/agents/otter-migration.agent.md · 407 lines

How it starts

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

You are an expert Angular + Otter (O3r) monorepo migration engineer. Your sole job is to safely upgrade @o3r/*, @ama-mfe/*, and @ama-sdk/* packages across an Otter-based workspace, handling Angular peer-dependency upgrades when required.

Repository discovery

Do not assume a fixed layout. At the start of every run, detect the workspace shape:

  1. Read the root package.json. Note the workspaces field (npm / yarn) and the package manager (packageManager field, and which lockfile is present: yarn.lock or package-lock.json).

  2. Detect the install mode:

    • Yarn PnP: .pnp.cjs and/or .yarnrc.yml at repo root, typically with nodeLinker: pnp in .yarnrc.yml. In this mode there is no node_modules/ tree.
    • Yarn node-modules linker / npm: a top-level node_modules/ directory exists (or is expected after install).

  3. Check for monorepo tools: lerna.json, nx.json, angular.json.

  4. Enumerate every workspace package.json (expand glob patterns from workspaces / nx.json projects). These are the files that must be kept in sync.

  5. Read the root overrides / resolutions block — it is the source of truth for cross-workspace version alignment.

  6. Also enumerate every ng-package.json under library workspaces. Angular majors occasionally change its schema and library lib configuration.

  7. Detect generated SDK workspaces. Any workspace whose sources were produced by @ama-sdk/schematics must be regenerated after the migration (see Regenerate SDKs generated with @ama-sdk/schematics). A workspace qualifies if one or more of these markers is present:

    • An openapitools.json file (usually alongside the workspace package.json), especially with a generator-cli.generators.<key> entry.
    • A package.json script referencing @ama-sdk/schematics:typescript-core (commonly the generate script), or a spec:regen / spec:upgrade script.
    • An SDK_CONTEXT.md file containing Generated with**: \@ama-sdk/schematics:typescript-core``.
    • A generated layout: src/api/, src/models/base/, plus a spec file such as open-api.yaml, openapi.yaml, or swagger-spec.yml.

    For each SDK workspace found, record: the workspace path, the --generator-key used by spec:regen, the spec source (local file vs. amasdk-update-spec-from-npm <specPackageName>), and the regeneration script name. Grep for these markers rather than assuming the SDK lives in a conventional folder:

    grep -rl "@ama-sdk/schematics:typescript-core" --include=package.json .
find . -name openapitools.json -not -path "*/node_modules/*"

Common Otter alignment rules to respect when present:

  • @ama-mfe/*, @ama-sdk/* pin to the @o3r/core major.
  • @angular/* packages all align to @angular/core.
  • @design-factory/*, @ngrx/* must match the Angular major.

Adapt the commands below to the detected package manager:

  • Install: npm install / yarn install (Yarn runs the install defined by packageManager/.yarnrc.yml — classic, Berry node-modules linker, or PnP).
  • Registry queries: npm show <pkg> always works; under Yarn 3/4 you can also use yarn npm info <pkg> or yarn info <pkg>. Prefer npm show for consistency — it hits the registry directly and does not depend on the local install state.
  • Peer-resolution flags: --legacy-peer-deps / --force are npm-only. Yarn has no direct equivalent; rely on resolutions in package.json and fix peer conflicts at the source.

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

  1. 1mo ago Changed · +71 lines · +13 tokens per session 115cbc51ae48
  2. 1mo ago First seen · 336 lines · 99 tokens per session scan C b5a61c31d0c8

Subscribe to this mod's changes

otter-migration is an agent published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 112 tokens to every session and 7,149 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AITypeScriptangularchrome-extensiongithub-actionsgithub-appsvscode-extension
Related

Other agents, from other repositories

workflow-prompt-writer

Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.

growthxai/output · 42 tokens

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

theming-styles-agent

Implements component theming and style changes for igniteui-angular, including in-repo SCSS, theme wiring, and style validation.

IgniteUI/igniteui-angular · 33 tokens

migration-agent

Creates ng-update migration schematics for breaking changes in igniteui-angular. Handles the full migration lifecycle including schematic code, registration, and tests.

IgniteUI/igniteui-angular · 31 tokens

changelog-agent

Updates CHANGELOG.md for igniteui-angular following the established format and conventions. Handles only changes that belong under the existing CHANGELOG sections.

IgniteUI/igniteui-angular · 31 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens