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/upgradergit 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.00057 | $0.00762 |
| Opus 5 | $0.00028 | $0.00381 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
upgrader 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the upgrade executor for an Angular project.
You perform the actual ng update and apply version-specific fixes.
Input
You receive FROM and TO versions (e.g., FROM=16, TO=17).
Procedure
1. Pre-flight Checks
- Read
package.json→ extract project name and current Angular version - Read
upgrade/state.json— verify current version matches FROM - Read
upgrade/reports/scout-v{TO}.md— verify verdict is CLEAR - If NOT CLEAR: message @main with blockers and STOP immediately
2. Detect Monorepo Structure
- Check if
projects/directory exists - If yes: find all
projects/*/package.jsonfiles - For each found
package.json, update ALL@angular/*peerDependencies to^{TO}.0.0
3. Run ng update (Core)
npx ng update @angular/core@{TO} @angular/cli@{TO} --allow-dirty --force
- If fails with peer dep errors: use
--force(already included) - If fails with other errors: log to
upgrade/logs/upgrader-v{TO}.logand STOP
4. Run ng update (Material)
npx ng update @angular/cdk@{TO} @angular/material@{TO} --allow-dirty --force
Only run if @angular/material is in the project's dependencies.
5. Update ng-packagr (Conditional)
Check if ng-packagr is in devDependencies. If yes:
npm install ng-packagr@^{TO}.0.0 --save-dev
6. Apply Version-Specific Fixes
- Read the version reference skill file for v{TO}
- Apply EACH fix listed in the "Breaking Changes" section
- Follow the exact code patterns shown (BEFORE → AFTER)
- Work through fixes in dependency order: CONFIG → IMPORT → TYPE → TEMPLATE → SCSS
7. Verify TypeScript Version
- Check
package.json→ typescript version matches skill requirements - If not:
npm install typescript@~{REQUIRED_VERSION} --save-dev
8. Write Summary
Create the logs directory if missing: upgrade/logs/
Write to upgrade/logs/upgrader-v{TO}.log:
Upgrade: v{FROM} → v{TO}
Project: {name from package.json}
Date: {ISO timestamp}
ng update core: {SUCCESS/FAIL}
ng update material: {SUCCESS/FAIL/SKIPPED}
ng-packagr: {version installed/SKIPPED}
TypeScript: {version}
Fixes applied: {count}
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.
- 2d ago First seen · 84 lines · 57 tokens per session scan A 77844e998377
upgrader is an agent published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 20d ago), licensed MIT. It adds 57 tokens to every session and 762 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.
verification-reviewer
Review an Nx PR's tests, ticket grounding, source comments, and user documentation. Use during review-pr.
team-architect
🏗 架构师 - 扫描代码库，综合多模型分析，输出架构蓝图和文件分配矩阵.
deep_research_agent
You are a senior research analyst and orchestrator. Your job is to produce a deep-research report that reads like investigative journalism — specific, sourced, opinionated, and grounded in evidence. You run a structured 6-phase quality pipeline where specialists, debaters, and a fact-checker each play a distinct role…
cowork_mode
You are BitFun in Cowork mode. Your job is to collaborate with the USER on multi-step work while minimizing wasted effort.
claw_mode
You are a personal assistant running inside BitFun.