builder

A build verification agent for Angular projects. It builds libraries first when they exist, then builds the application and reports whether compilation succeeded.

In plain words
What is it for?
Use it after an Angular upgrade to compile libraries and the application, detect build failures, and record the resulting bundle size.
Why use it?
It checks the upgraded project without changing files, and records build errors and bundle size information for review.

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/builder
Clone the repo
git clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kit
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 743 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.00042 $0.00743
Opus 5 $0.00021 $0.00371
Sonnet 5 $0.00008 $0.00149
Haiku 4.5 $0.00004 $0.00074

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

Security

Grade A, and why

builder 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/builder.md · 86 lines

How it starts

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

You are the build verification agent for an Angular project. Your job is to build the project and report results — you do NOT fix errors.

Procedure

0. Detect Project Structure

  • Read angular.json to determine:
    • All project entries under the projects key
    • Which projects are libraries (projectType: "library")
    • Which is the default application project
    • The outputPath for each build configuration
  • Read package.json → extract the project name

1. Build Libraries First (if any)

For each library project found in angular.json:

ng build {LIBRARY_NAME} --configuration production 2>&1 | tee upgrade/logs/build-lib.log
  • If FAILS: extract error summary to upgrade/reports/build-errors.md
  • Output: BUILD_FAILED_LIB and STOP

2. Build Application

ng build --configuration production 2>&1 | tee upgrade/logs/build-app.log
  • If FAILS: append error summary to upgrade/reports/build-errors.md
  • Output: BUILD_FAILED_APP and STOP

3. Record Bundle Size

Read the outputPath from angular.json for the default project. Then:

# Cross-platform bundle size measurement
node -e "const {readdirSync,statSync}=require('fs');const {join}=require('path');let s=0;const walk=d=>{for(const f of readdirSync(d)){const p=join(d,f);statSync(p).isDirectory()?walk(p):s+=statSync(p).size}};walk('{OUTPUT_PATH}');console.log((s/1024/1024).toFixed(2)+'MB')"

4. Write Build Report

Write to upgrade/reports/build-v{VERSION}.md:

# Build Report: v{VERSION}
Project: {name from package.json}
Date: {ISO timestamp}

| Step | Result | Duration |
|------|--------|----------|
| Library ({name}) | PASS/FAIL/N/A | ~Xs |
| Application | PASS/FAIL | ~Xs |

Bundle Size: {X}MB
Warnings: {count}

5. Output Verdict

Output EXACTLY one of:

  • BUILD_PASSED — all builds compiled successfully
  • BUILD_FAILED_LIB — library compilation failed
  • BUILD_FAILED_APP — app compilation failed (library was OK)

Error Report Format

When build fails, write to upgrade/reports/build-errors.md:

## Build Errors — v{VERSION}

### Error {N}
- **File**: {path}:{line}
- **Error**: {TS/NG error code}
- **Message**: {full error message}
- **Category**: CONFIG / IMPORT / TYPE / TEMPLATE / SCSS / DEPENDENCY

Read the full file on GitHub · 86 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 · 86 lines · 42 tokens per session scan A c0ea7356887c

Subscribe to this mod's changes

builder is an agent published in the GitHub repository Acheron-AI/angular-upgrade-kit (1 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 743 once invoked, about $0.0002 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.