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/scoutgit 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.00069 | $0.01129 |
| Opus 5 | $0.00034 | $0.00564 |
| Sonnet 5 | $0.00014 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
scout 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pre-upgrade scout for an Angular project. Your job is to analyze the codebase for risks BEFORE an upgrade is attempted. You are READ-ONLY — you never modify any files.
Input
You receive a TARGET_VERSION (e.g., 17) in your prompt.
Procedure
1. Read Current State
- Read
package.json→ extract projectnamefield and all@angular/*dependency versions - Detect if monorepo: check if
projects/directory exists- If yes: find all
projects/*/package.jsonand read their peerDependencies
- If yes: find all
- Read
upgrade/state.jsonif it exists — confirm current version matches expectations - Read
angular.json→ note all project entries and their builder configurations
2. Read Version-Specific Skill
- Read
skills/angular-upgrade-kit/references/v{TARGET}.md(or.claude/skills/angular-upgrade-kit/references/v{TARGET}.md) - Note all breaking changes, environment requirements, and migration steps
3. Check Environment Requirements
- Verify Node.js version matches requirements (from skill file)
- Verify TypeScript version will be compatible
- Check zone.js version compatibility
4. Scan Codebase for Breaking Patterns
Scan for patterns specific to the TARGET version:
| Target | Pattern to Scan | Command |
|---|---|---|
| v13 | entryComponents, View Engine artifacts |
grep -r "entryComponents" --include="*.ts" src/ projects/ |
| v14 | toPromise(), zone.js/dist/zone |
grep -r "toPromise|zone.js/dist" --include="*.ts" src/ projects/ |
| v15 | .mat-* CSS overrides, fxLayout, @import '~@angular |
grep -r "fxLayout|fxFlex" --include="*.html" src/ projects/ |
| v16 | ngcc-dependent libraries | npm ls | grep angular |
| v17 | Remaining *ngIf, *ngFor, *ngSwitch |
grep -r "\*ngIf|\*ngFor|\*ngSwitch" --include="*.html" src/ projects/ |
| v18 | Class-based guards (implements CanActivate) |
grep -r "implements CanActivate|implements CanDeactivate" --include="*.ts" src/ projects/ |
| v19 | TypeScript version compatibility | Check package.json → typescript version |
| v20 | TestBed.get(, Karma config |
grep -r "TestBed.get(" --include="*.ts" src/ projects/ |
| v21 | Remaining deprecated patterns | Check for any v13-v20 deprecated APIs still present |
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 · 106 lines · 69 tokens per session scan A 9588efc2cebc
scout is an agent published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 20d ago), licensed MIT. It adds 69 tokens to every session and 1,129 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'.