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 skills add Phaedra-Solutions/cursor-rules --skill upgrade-angulargit clone --depth 1 https://github.com/Phaedra-Solutions/cursor-rulesWrote 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/phaedra-solutions/cursor-rules/upgrade-angular)<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-angular"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-angular/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.
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-angular"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-angular.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00105 | $0.03036 |
| Opus 5.5 | $0.00042 | $0.01214 |
| Sonnet 5.5 | $0.00021 | $0.00607 |
| Haiku 4.5 | $0.00011 | $0.00304 |
Grade A, and why
upgrade-angular 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Angular
When to use
- The user asks to upgrade Angular, or to move off an unsupported or vulnerable version (v19 and older are unsupported; v20 support ends 28 Nov 2026).
- The installed
@angular/coreis below theapplies_torange offrontend/angularand the user agrees to upgrade. - The user asks to modernize an NgModule app (standalone, control flow, signals, zoneless, Vitest).
For a patch within the same major, run ng update @angular/core@<major> @angular/cli@<major> and go to Verify. For AngularJS (angular 1.x), this skill doesn't apply.
Before you start
- Read exact versions from the lockfile: every
@angular/*package,@angular/material/@angular/cdk,@angular-devkit/*,typescript,rxjs,zone.js, SSR packages (@angular/ssr,@nguniversal/*), the test runner (Karma, Jest, Vitest), and third-party Angular libraries (ngx-*,@ngrx/*, component libraries). Read the Node version from.nvmrc,engines, the Dockerfile and CI. - The working tree must be clean. Ask the user to commit or stash first; work on a new branch (for example
chore/angular-22). - Ask the user:
- the target (default: latest 22.x, currently 22.2.4) and whether to stop after each major for review;
- whether to run the modernization migrations (standalone, control flow, signals, zoneless, Vitest) after the version hops, and which ones. They're separate steps, never mixed into a version hop;
- whether network installs are approved. Follow the release-age cooldown in
core/supply-chain; a security patch inside the cooldown needs the user's explicit exception.
- Check every third-party Angular library supports each target major (its
peerDependencieson npm). List any that don't, with alternatives, before starting. Don't start a hop a required library can't follow. - Plan the hops: one major at a time (for example 15 → 16 → 17 → … → 22). Open the update guide (
https://angular.dev/update-guide) for each hop with the right "from", "to" and options, and follow its checklist. - Plan runtimes per hop:
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.
- 3d ago First seen · 137 lines · 105 tokens per session scan A f0d7b38f367c
upgrade-angular is a skill published in the GitHub repository Phaedra-Solutions/cursor-rules (4 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 3,036 once invoked, about $0.0004 per session on Opus 5.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-11-01.
Other skills, from other repositories
mcp-server-patterns
Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
claude-api
Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.
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…
nestjs
Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…
prisma-orm
Use when modeling data or writing type-safe queries with Prisma ORM in TypeScript — schema.prisma, prisma.config.ts, the generated Prisma Client, and Prisma Migrate, including the v6 to v7 upgrade. NOT schema-as-TS with a SQL builder (that is drizzle-orm), NOT ORM-agnostic zero-downtime migration (that is…