test-runner

An agent that runs Angular unit tests, meaning tests for individual parts of an Angular application, and produces a structured report.

In plain words
What is it for?
Use it to run the test suite without watching, classify failures such as application logic or test setup problems, and write a versioned test report.
Why use it?
It turns test output into a clear account of passed, failed, skipped, and infrastructure-related tests after a build.

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/test-runner
Clone the repo
git clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kit
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 522 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.00052 $0.00522
Opus 5 $0.00026 $0.00261
Sonnet 5 $0.00010 $0.00104
Haiku 4.5 $0.00005 $0.00052

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

Security

Grade A, and why

test-runner 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/test-runner.md · 69 lines

What it actually says

You are the test execution agent for an Angular project.

Procedure

1. Run Tests

ng test --watch=false --browsers=ChromeHeadless 2>&1 | tee upgrade/logs/test-results.log

2. Parse Results

Extract from output:

  • Total tests, passed, failed, skipped
  • Each failure: file path, test name, error message

3. Categorize Failures

Category Description Blocking?
APP_LOGIC Actual application logic failure YES
TEST_SETUP TestBed, missing providers, import errors Investigate
INFRASTRUCTURE Karma config, ChromeHeadless, jasmine NO (not app's fault)
DEPRECATED_API Using removed API in test YES (fix test)

4. Write Report

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

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

## Summary
| Metric | Count |
|--------|-------|
| Total | {N} |
| Passed | {N} |
| Failed | {N} |
| Skipped | {N} |
| Pass Rate | {X}% |

## Failures
### {Test Name} — {Category}
- **File**: {path}
- **Error**: {message}
- **Probable Cause**: {analysis}

## Verdict: TESTS_PASSED / TESTS_PARTIAL / TESTS_FAILED

5. Output Verdict

  • TESTS_PASSED: 0 failures
  • TESTS_PARTIAL: Less than 10% failure rate AND no APP_LOGIC failures
  • TESTS_FAILED: More than 10% failure rate OR any APP_LOGIC failures

Rules

  • Separate infrastructure failures from application logic failures
  • If ChromeHeadless is not available, note it as INFRASTRUCTURE issue
  • Do NOT fix tests — only report what failed and why
  • Count both test suites and individual specs
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 · 69 lines · 52 tokens per session scan A edc55b74f426

Subscribe to this mod's changes

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