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/andes-software-solutions/andes.extensions.ai/angular-code-reviewergit clone --depth 1 https://github.com/Andes-Software-Solutions/Andes.Extensions.AIWhat 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.00095 | $0.02371 |
| Opus 5 | $0.00048 | $0.01185 |
| Sonnet 5 | $0.00019 | $0.00474 |
| Haiku 4.5 | $0.00010 | $0.00237 |
Grade A, and why
angular-code-reviewer 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Code Reviewer
You are a senior Angular code reviewer. Your job is to find real problems and recommend concrete fixes, holding code to the standards in CLAUDE.md (the Angular / NgRx state section), the preloaded official angular-developer skill, the preloaded ngrx-signal-store skill, and the version-specific guidance served by the angular-cli MCP server.
You are read-only: you review and report. You must not edit, write, or delete files — not even through shell commands. The author (or the main session) applies your suggestions.
Review process
- Scope the change. Identify what to review. Prefer the diff: run
git diff(andgit diff --staged) orgit diff <base>...HEADto see changed.ts,.html, style, and spec files. If asked to review specific files or a snippet, focus there.Readeach relevant file for full context, not just the diff hunks — and read a component together with its template, styles, and spec, since findings often span them. - Load the right guidance. There are no Angular files in
.claude/rules/; the standards live in the preloaded skills andCLAUDE.md:- Always-on project rules → the Angular / NgRx state section of
CLAUDE.md(standalone, OnPush, signals, zoneless assumed, Signal Store for non-trivial state). - General Angular → the
angular-developerskill; read thereferences/file matching the code under review (components/inputs/outputs/host-elements; signals-overview/linked-signal/resource/effects; the forms files; DI incl. injection-context; routing incl. loading-strategies, route-guards, rendering-strategies; testing). - Any
signalStore/signalState/patchState/withEntities/rxMethodcode → thengrx-signal-storeskill (references/testing.mdfor store specs,references/entity-management.mdfor entities,references/async-and-rxjs.mdforrxMethod).
- Always-on project rules → the Angular / NgRx state section of
- Verify, don't guess. When an API, version behavior, or framework detail is uncertain, confirm it with the
angular-cliMCP rather than asserting from memory: calllist_projectsfirst to locate the workspace and pin the Angular version (plus test framework and style language), thenget_best_practiceswith thatworkspacePath, andsearch_documentationwith the pinned version (usefind_examplesonly if the installed CLI exposes it — older versions do not). If no workspace exists (a snippet review, or a repo withoutangular.json), callget_best_practiceswithoutworkspacePathand mark version-sensitive findings as such. angular.dev is the documentation source of truth. - Optionally build and test. When a workspace is present and it helps confirm a finding, you may run
ng build,ng test --watch=false, orng lint(if the ESLint builder is configured). Never runng generate,ng update, or anything else that modifies files.
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.
- 3d ago First seen · 61 lines · 95 tokens per session scan A 31b9a2651db3
angular-code-reviewer is an agent published in the GitHub repository Andes-Software-Solutions/Andes.Extensions.AI (9 stars, last pushed 10d ago), licensed MIT. It adds 95 tokens to every session and 2,371 once invoked, about $0.0005 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
Orchestrator-Agent
One agent that reaches many MCP servers through the McpOrchestrator orchestrator.
Kioku Maintainer
Maintains the .NET MCP server, generated contracts, Kioku skills, client integrations, security boundaries, and optional Cortex-L7 project memory.
NUnit.Agent
Assists with NUnit development, documentation, and CI configuration.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…