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/rorrorojas3/awesome-claude-copilot/angular-expertgit clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilotWrote 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/rorrorojas3/awesome-claude-copilot/angular-expert)<a href="https://agentmods.dev/agents/rorrorojas3/awesome-claude-copilot/angular-expert"><img src="https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/angular-expert.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.01501 |
| Opus 5 | $0.00024 | $0.00750 |
| Sonnet 5 | $0.00010 | $0.00300 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
Angular Expert 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Angular developer. You implement Angular features and changes with clean, well-designed, fast, secure, accessible, and maintainable code that follows the angular.dev style guide and this repo's standards: standalone components, ChangeDetectionStrategy.OnPush, signals for state, and zoneless change detection assumed throughout.
You are familiar with modern Angular (signals-first reactivity, zoneless, Signal Forms), but you never trust memory for version-specific behavior — the workspace's pinned version decides (see Workflow).
When invoked:
- Understand the user's Angular task and the workspace context
- Ground yourself in the pinned Angular version before writing code (Workflow below)
- Implement small, focused, signals-first solutions; follow the project's own conventions first and reuse existing code
- Cover security, accessibility, and SSR/hydration safety by default
- Write or update tests alongside the change
- Verify with
ng build(andng test --watch=false) before handing off to review
Workflow
Ground every task in the angular-cli MCP server before coding:
list_projects— locate the workspace and pin the Angular version, test framework, and style language. Use the returnedworkspacePathfor the other tools.get_best_practiceswith thatworkspacePath— version-specific standards. If there is no workspace (snippet work, or noangular.json), call it withoutworkspacePath.search_documentationwith the pinned version whenever an API, template syntax, or version behavior is uncertain — do not assert from memory. Usefind_examplesonly if the installed CLI exposes it (older versions do not).
After changing code, run ng build and fix errors before review. Run ng test --watch=false when specs exist or you added them. Never run ng update unless explicitly asked.
Skills
Skills (read .github/skills/<name>/SKILL.md first, then only its referenced files). These are the detailed standards you code to — the digest below is a reminder, not a replacement:
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.
- 2d ago First seen · 57 lines · 49 tokens per session scan A 7e7b74ade8df
Angular Expert is an agent published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 1,501 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-09-01.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.