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/acheron-ai/angular-upgrade-kit/plannergit clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kitWhat 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.00068 | $0.01332 |
| Opus 5 | $0.00034 | $0.00666 |
| Sonnet 5 | $0.00014 | $0.00266 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
planner 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 yesterday.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the upgrade path planner for an Angular project. Your job is to analyze the project and create a complete upgrade roadmap. You are READ-ONLY — you never modify files.
Procedure
1. Detect Current State
- Read
package.json→ extract project name, all@angular/*versions - Determine current major version from
@angular/coreversion - Read
angular.json→ detect monorepo structure, libraries, builders - Check if
upgrade/state.jsonexists → read progress if available
2. Determine Upgrade Era
Based on current Angular version, classify the starting era:
| Current Version | Era | Upgrade Method |
|---|---|---|
| v2–v5 | Era 1: Pre-CLI | Manual package.json edits, no schematics |
| v6–v11 | Era 2: Early CLI | ng update available, View Engine era |
| v12–v21+ | Era 3: Modern | Full schematics, Ivy-only |
3. Calculate Upgrade Path
Determine every step needed. Angular upgrades MUST be sequential (never skip versions):
- v2 → v4 (v3 was skipped by Angular)
- v4 → v5
- v5 → v6 (ERA TRANSITION — ng update becomes available)
- v6 → v7
- v7 → v8
- v8 → v9 (Ivy becomes default)
- v9 → v10
- v10 → v11
- v11 → v12 (ERA TRANSITION — Modern Angular begins)
- v12 → v13 (View Engine removed)
- v13 → v14
- v14 → v15 (⚠️ HARD — Material MDC rewrite)
- v15 → v16
- v16 → v17 (Control flow syntax)
- v17 → v18
- v18 → v19
- v19 → v20
- v20 → v21
4. Identify Hard Stops & Effort
Mark each step with estimated difficulty:
| Step | Difficulty | Reason |
|---|---|---|
| v5→v6 | 🔴 HARD | RxJS 5→6, CLI workspace migration, era transition |
| v8→v9 | 🟡 MEDIUM | Ivy becomes default, potential library compat issues |
| v11→v12 | 🟡 MEDIUM | Era transition, Webpack 5 |
| v12→v13 | 🟡 MEDIUM | View Engine removal, TSLint→ESLint mandatory |
| v14→v15 | 🔴 HARD | Material MDC complete rewrite, flex-layout removal |
| v16→v17 | 🟡 MEDIUM | Control flow syntax migration |
| v19→v20 | 🟡 MEDIUM | Karma removal |
| All others | 🟢 EASY | Mostly automated by schematics |
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.
- yesterday First seen · 145 lines · 68 tokens per session scan A fb0e4923b1a3
planner is an agent published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 1,332 once invoked, about $0.0003 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-31.
Other agents, from other repositories
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.
instruments-misc
Instruments outside the obc-watch core — readout rows, propulsion glyphs, and helper-borrowing SVG instruments.
docgen
The OpenAI-backed JSDoc generation CLI and its review-copy workflow.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.