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 commands/acheron-ai/angular-upgrade-kit/upgrade-plangit 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-plan)<a href="https://agentmods.dev/commands/acheron-ai/angular-upgrade-kit/upgrade-plan"><img src="https://agentmods.dev/badge/commands/acheron-ai/angular-upgrade-kit/upgrade-plan.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 | $0.00013 | $0.00225 |
| Opus 5 | $0.00006 | $0.00112 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
upgrade-plan 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.
What it actually says
Generate a complete upgrade roadmap from the current Angular version to the latest.
Read package.json to detect the current Angular version.
Use the planner subagent to analyze the full upgrade path.
The planner will:
- Detect the current Angular version and era (Pre-CLI, Early CLI, or Modern)
- Calculate every sequential step needed to reach the latest version
- Identify hard stops (v5→v6 era transition, v14→v15 MDC, v16→v17 control flow)
- Map Node.js version switches needed
- Audit third-party dependencies for compatibility risks
- Estimate effort per step (easy/medium/hard)
- Write a complete roadmap to
upgrade/plan.md
After the planner completes, display the summary:
- Total steps
- Estimated total effort
- Key risks and hard stops
- Recommended Node.js version management (nvm)
Then ask the user: "Ready to start? Run /upgrade-to {NEXT_VERSION} to begin."
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 · 26 lines · 13 tokens per session scan A 8acd362d2353
upgrade-plan is a command published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 21d ago), licensed MIT. It adds 13 tokens to every session and 225 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
create-workflow
Scaffold a custom workflow — generates a mode skill and shortcut command.
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
create
Scaffold a new plugin with directory structure, manifests, and marketplace registration.
refine
Run recursive refinement on the current branch and PR.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
develop
Implement skill development issues with TDD-governed workflow.