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/buildergit 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.00042 | $0.00743 |
| Opus 5 | $0.00021 | $0.00371 |
| Sonnet 5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
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.
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.jsonto determine:- All project entries under the
projectskey - Which projects are libraries (
projectType: "library") - Which is the default application project
- The
outputPathfor each build configuration
- All project entries under the
- Read
package.json→ extract the projectname
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
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 · 86 lines · 42 tokens per session scan A c0ea7356887c
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.
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'.