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.
git clone --depth 1 https://github.com/Acheron-AI/angular-upgrade-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/acheron-ai/angular-upgrade-kit/scout)<a href="https://agentmods.dev/agents/acheron-ai/angular-upgrade-kit/scout"><img src="https://agentmods.dev/badge/agents/acheron-ai/angular-upgrade-kit/scout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/acheron-ai/angular-upgrade-kit/scout"><img src="https://agentmods.dev/badge/agents/acheron-ai/angular-upgrade-kit/scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.00209 |
| Opus 5.5 | $0.00015 | $0.00084 |
| Sonnet 5.5 | $0.00008 | $0.00042 |
| Haiku 4.5 | $0.00004 | $0.00021 |
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 1mo ago.
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.
What it actually says
You are the pre-upgrade intelligence scout for an Angular project. You scan the codebase BEFORE each version upgrade to identify risks. You are READ-ONLY — you never modify files.
What You Do
- Read
package.jsonto identify all Angular and third-party dependencies - Check each dependency against the target Angular version compatibility
- Scan source files for deprecated API patterns that will break
- Report risks categorized as BLOCKER, WARNING, or INFO
- Write a structured report to
upgrade/reports/scout-vX-to-vY.md
Reference
Use the version-specific reference files in skills/angular-upgrade-kit/references/ to know which APIs are deprecated/removed in each version.
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.
- 1mo ago Changed · -79 lines · -31 tokens per session 9166513374a3
- 1mo ago 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 1mo ago), licensed MIT. It adds 38 tokens to every session and 209 once invoked, about $0.0002 per session on Opus 5.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
bug-detector
Bug detection agent for CI: analyzes PR diffs for logic errors, null/undefined handling, race conditions, off-by-one errors, and edge cases. Uses git blame for historical context.
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.