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.
git clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kitWrote 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/commands/acheron-ai/angular-upgrade-kit/upgrade-controlflow)<a href="https://agentmods.dev/commands/acheron-ai/angular-upgrade-kit/upgrade-controlflow"><img src="https://agentmods.dev/badge/commands/acheron-ai/angular-upgrade-kit/upgrade-controlflow.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.1 | $0.00016 | $0.00310 |
| Opus 5 | $0.00008 | $0.00155 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
upgrade-controlflow 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 6d 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.
What it actually says
Execute the Angular 17 control flow migration after the core v17 upgrade.
This runs the automatic migration schematic that converts *ngIf, *ngFor, *ngSwitch to the new @if, @for, @switch syntax.
Read angular.json to detect all project paths (libraries and app).
-
For each library project found in angular.json: Run:
ng generate @angular/core:control-flow-migration --path={LIBRARY_PATH} -
For the main application: Run:
ng generate @angular/core:control-flow-migration --path=src -
Verify:
grep -r "\*ngIf\|\*ngFor\|\*ngSwitch" --include="*.html" src/ projects/— should be zero results -
If any remain, fix them manually using the new syntax.
-
Audit @for track expressions: Use a subagent to scan all
@forblocks in HTML files.- Change
track $indextotrack item.idwhere items have anidproperty - Keep
track $indexonly for primitive arrays or when no unique key exists
- Change
-
Build and verify with builder subagent.
-
If build passes, run test-runner and ui-tester in parallel.
-
Use verifier for GO/NO-GO.
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.
- 6d ago First seen · 29 lines · 16 tokens per session scan A 7058b108291b
upgrade-controlflow is a command published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 310 once invoked, about $0.0001 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 commands, from other repositories
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
form-designer
Use when a form is losing people. Too many fields, validation that interrupts typing, unclear required fields, a multi-step flow with no sense of progress, or inputs with no labels.
healthcare-ux-specialist
Use when designing clinical or patient-facing interfaces. Clinical workflows, displaying sensitive patient data, HIPAA considerations in the UI, and medical terminology patients do not speak.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.