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 skills/rorrorojas3/awesome-claude-copilot/angular-developernpx skills add RorroRojas3/awesome-claude-copilot --skill angular-developergit clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilotWhat 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.00068 | $0.02116 |
| Opus 5 | $0.00034 | $0.01058 |
| Sonnet 5 | $0.00014 | $0.00423 |
| Haiku 4.5 | $0.00007 | $0.00212 |
Grade A, and why
angular-developer 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.
This is a copy
88% identical to angular-developer — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Developer Guidelines
-
Always analyze the project's Angular version before providing guidance, as best practices and available features can vary significantly between versions. If creating a new project with Angular CLI, do not specify a version unless prompted by the user.
-
When generating code, follow Angular's style guide and best practices for maintainability and performance. Use the Angular CLI for scaffolding components, services, directives, pipes, and routes to ensure consistency.
-
Once you finish generating code, run
ng buildto ensure there are no build errors. If there are errors, analyze the error messages and fix them before proceeding. Do not skip this step, as it is critical for ensuring the generated code is correct and functional.
Creating New Projects
If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project:
- Use the latest stable version of Angular unless the user specifies otherwise.
- Use Signals Forms for form management in new projects (available in Angular v21 and newer) Find out more.
Execution Rules for ng new:
When asked to create a new Angular project, you must determine the correct execution command by following these strict steps:
Step 1: Check for an explicit user version.
- IF the user requests a specific version (e.g., Angular 15), bypass local installations and strictly use
npx. - Command:
npx @angular/cli@<requested_version> new <project-name>
Step 2: Check for an existing Angular installation.
- IF no specific version is requested, run
ng versionin the terminal to check if the Angular CLI is already installed on the system. - IF the command succeeds and returns an installed version, use the local/global installation directly.
- Command:
ng new <project-name>
Step 3: Fallback to Latest.
- IF no specific version is requested AND the
ng versioncommand fails (indicating no Angular installation exists), you must usenpxto fetch the latest version. - Command:
npx @angular/cli@latest new <project-name>
What ships with it
37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/angular-animations.md 3.9 KB
- references/angular-aria.md 18 KB
- references/cli.md 3.6 KB
- references/component-harnesses.md 2.7 KB
- references/component-styling.md 2.5 KB
- references/components.md 3.3 KB
- references/creating-services.md 2.8 KB
- references/data-resolvers.md 1.6 KB
- references/define-routes.md 1.7 KB
- references/defining-providers.md 2.2 KB
- references/di-fundamentals.md 3.4 KB
- references/e2e-testing.md 884 B
- references/effects.md 2.7 KB
- references/environment-configuration.md 3.2 KB
- references/hierarchical-injectors.md 2.1 KB
- references/host-elements.md 2.1 KB
- references/injection-context.md 1.9 KB
- references/inputs.md 2.4 KB
- references/linked-signal.md 2.6 KB
- references/loading-strategies.md 1.4 KB
- references/mcp.md 3.7 KB
- references/migrations.md 2.0 KB
- references/navigate-to-routes.md 1.6 KB
- references/outputs.md 2.6 KB
- references/reactive-forms.md 3.5 KB
- references/rendering-strategies.md 1.8 KB
- references/resource.md 2.6 KB
- references/route-animations.md 1.6 KB
- references/route-guards.md 1.4 KB
- references/router-lifecycle.md 1.5 KB
- references/router-testing.md 3.7 KB
- references/show-routes-with-outlets.md 1.6 KB
- references/signal-forms.md 27 KB
- references/signals-overview.md 2.8 KB
- references/tailwind-css.md 1.8 KB
- references/template-driven-forms.md 3.7 KB
- references/testing-fundamentals.md 2.5 KB
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.
- yesterday First seen · 132 lines · 68 tokens per session scan A 36719c2cce98
angular-developer is a skill published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 2,116 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to angular-developer, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…