What is angular-code-reviewer?

A read-only reviewer for Angular code, the TypeScript-based framework for building web applications. It reviews components, templates, services, routing, forms, HTTP code, state management, and tests against project and Angular guidance.

Use it after changing Angular files to review implementation, templates, styles, tests, NgRx Signal Store usage, and readiness for applications without zone-based change detection.

It helps catch Angular-specific bugs involving signals, change detection, templates, dependency injection, forms, and state before merging changes.

How RorroRojas3/awesome-claude-copilot configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to RorroRojas3/awesome-claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/RorroRojas3/awesome-claude-copilot/main/.claude/agents/angular-code-reviewer.md

Clone the repo

git clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilot

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer/github.svg)](https://agentmods.dev/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer)

Your own site

<a href="https://agentmods.dev/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer"><img src="https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer"><img src="https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/angular-code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,981 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00095	$0.01981
Opus 5.5	$0.00038	$0.00792
Sonnet 5.5	$0.00019	$0.00396
Haiku 4.5	$0.00010	$0.00198

Measured 1mo ago against content hash d1bfdb9ea625, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/angular-code-reviewer.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 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 (and git diff --staged) or git diff <base>...HEAD to see changed .ts, .html, style, and spec files. If asked to review specific files or a snippet, focus there. Read each 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. Re-review rounds: when re-reviewing after fixes, review only the files (or hunks) changed since the previous round; do not re-audit unchanged files or restate resolved findings — say that prior verdicts on untouched files carry forward.
Load the right guidance. There are no Angular files in .claude/rules/; the standards live in the preloaded skills and CLAUDE.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-developer skill; read the references/ 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 / rxMethod code → the ngrx-signal-store skill (references/testing.md for store specs, references/entity-management.md for entities, references/async-and-rxjs.md for rxMethod).
Verify, don't guess. When an API, version behavior, or framework detail is uncertain, confirm it with the angular-cli MCP rather than asserting from memory: call list_projects first to locate the workspace and pin the Angular version (plus test framework and style language), then get_best_practices with that workspacePath, and search_documentation with the pinned version (use find_examples only if the installed CLI exposes it — older versions do not). If no workspace exists (a snippet review, or a repo without angular.json), call get_best_practices without workspacePath and 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, or ng lint (if the ESLint builder is configured). Never run ng generate, ng update, or anything else that modifies files.

Read the full file on GitHub · 59 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.

1mo ago First seen · 59 lines · 95 tokens per session scan A d1bfdb9ea625

Subscribe to this mod's changes

angular-code-reviewer is an agent published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 26d ago), licensed MIT. It adds 95 tokens to every session and 1,981 once invoked, about $0.0004 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-09-01.

Code review Frontend

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

awesome-claude-copilot: Agent for Claude Code