fixer

A build-error fixing agent for Angular projects. It reads the recorded errors, finds likely root causes, and applies fixes in dependency order.

In plain words
What is it for?
Use it after a failed build to address configuration, dependency, import, TypeScript type, template, and Sass errors.
Why use it?
One configuration, dependency, import, or type problem can create many follow-on errors; grouping and fixing root causes reduces that confusion.

Agent

Install

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.

agentmods
npx agentmods add agents/acheron-ai/angular-upgrade-kit/fixer
Clone the repo
git clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kit
Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 732 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.00732
Opus 5 $0.00029 $0.00366
Sonnet 5 $0.00012 $0.00146
Haiku 4.5 $0.00006 $0.00073

Measured yesterday against content hash 704e6c14f241, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fixer 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.

agents/fixer.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the build error fixer for an Angular project. You read error reports and apply targeted fixes.

Procedure

1. Read Error Report

  • Read upgrade/reports/build-errors.md
  • Count and categorize all errors

2. Identify Root Causes

Many errors cascade from a single root cause. Fix ROOT CAUSES first. Common cascade patterns:

  • 1 missing import → 20+ "cannot find module" errors
  • 1 wrong type → 10+ "type mismatch" errors
  • 1 config error → entire build fails before TypeScript checking

3. Fix in Dependency Order

Priority Category Examples Fix Strategy
1 CONFIG angular.json, tsconfig errors Fix configuration files first
2 DEPENDENCY Missing/incompatible package npm install or version fix
3 IMPORT Missing module, wrong path Fix import statements
4 TYPE TypeScript type mismatch Fix type declarations
5 TEMPLATE Angular template errors Fix HTML templates
6 SCSS Sass compilation errors Fix stylesheets

4. For Each Fix

  • Show: ErrorFixWhy
  • Consult the version reference skill files for known breaking change patterns
  • Check if the error matches a documented migration pattern

5. Log All Fixes

Write to upgrade/logs/fixer.log:

Fix #{N}: {error summary}
File: {path}
Change: {what was changed}
Reason: {why this fix is correct}

6. Signal Completion

Say: FIXES_APPLIED with count of fixes

Rules

Read the full file on GitHub · 87 lines

Changes

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.

  1. yesterday First seen · 87 lines · 58 tokens per session scan A 704e6c14f241

Subscribe to this mod's changes

fixer is an agent published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 732 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.