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/sajeetharan/angular-agent-kit/angular-best-practicesnpx skills add sajeetharan/angular-agent-kit --skill angular-best-practicesgit clone --depth 1 https://github.com/sajeetharan/angular-agent-kitWhat 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.00079 | $0.01617 |
| Opus 5 | $0.00039 | $0.00809 |
| Sonnet 5 | $0.00016 | $0.00323 |
| Haiku 4.5 | $0.00008 | $0.00162 |
Grade A, and why
angular-best-practices 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Best Practices
Comprehensive performance optimization and modern Angular guide, containing 55+ rules across 12 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new Angular components or services
- Implementing change detection strategies
- Reviewing code for performance issues
- Refactoring existing Angular code
- Optimizing bundle size or load times
- Working with RxJS observables and state management
- Implementing forms and validation
- Writing unit and integration tests
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Signals & Reactivity | CRITICAL | signals- |
| 2 | Change Detection | CRITICAL | cd- |
| 3 | Bundle Size Optimization | CRITICAL | bundle- |
| 4 | Template Performance | HIGH | template- |
| 5 | RxJS & Async Operations | HIGH | rxjs- |
| 6 | Component Architecture | HIGH | component- |
| 7 | Dependency Injection | HIGH | di- |
| 8 | Routing & Navigation | MEDIUM | routing- |
| 9 | HTTP & Data Fetching | MEDIUM | http- |
| 10 | Forms & Validation | MEDIUM | forms- |
| 11 | Accessibility | MEDIUM | a11y- |
| 12 | Testing & Debugging | MEDIUM | testing- |
| 13 | Tooling | MEDIUM | tooling- |
Quick Reference
1. Signals & Reactivity (CRITICAL)
signals-overview- Use signals for reactive state managementsignals-linked-signal- Use linkedSignal for dependent writable statesignals-resource- Use resource for async data fetchingsignals-effects- Use effects only for side effects, never for state sync
2. Change Detection (CRITICAL)
cd-onpush- Use OnPush change detection strategycd-trackby- Always use trackBy in *ngForcd-pure-pipes- Prefer pure pipes over methods in templatescd-immutable-data- Use immutable data patternscd-detach-reattach- Detach change detection for heavy computationscd-run-outside-angular- Run non-UI code outside NgZone
What ships with it
44 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.
- AGENTS.md 20 KB
- metadata.json 356 B
- README.md 4.2 KB
- rules/_sections.md 3.1 KB
- rules/_template.md 962 B
- rules/a11y-angular-aria.md 2.5 KB
- rules/bundle-avoid-barrel-exports.md 3.0 KB
- rules/bundle-defer-views.md 3.4 KB
- rules/bundle-lazy-loading.md 3.2 KB
- rules/bundle-preload-strategies.md 3.8 KB
- rules/bundle-standalone-components.md 3.1 KB
- rules/bundle-tree-shaking.md 2.6 KB
- rules/cd-detach-reattach.md 3.4 KB
- rules/cd-immutable-data.md 3.2 KB
- rules/cd-onpush.md 2.1 KB
- rules/cd-pure-pipes.md 3.0 KB
- rules/cd-run-outside-angular.md 4.1 KB
- rules/cd-trackby.md 2.4 KB
- rules/component-signal-inputs.md 2.4 KB
- rules/component-smart-presentational.md 3.9 KB
- rules/di-inject-function.md 1.9 KB
- rules/forms-reactive-over-template.md 4.3 KB
- rules/forms-signal-forms.md 2.4 KB
- rules/http-interceptors.md 3.9 KB
- rules/routing-guards.md 1.9 KB
- rules/routing-rendering-strategies.md 1.7 KB
- rules/rxjs-avoid-nested-subscriptions.md 3.5 KB
- rules/rxjs-debounce-throttle.md 4.3 KB
- rules/rxjs-share-replay.md 4.1 KB
- rules/rxjs-signals-vs-observables.md 4.0 KB
- rules/rxjs-switchmap-vs-mergemap.md 4.1 KB
- rules/rxjs-unsubscribe.md 3.7 KB
- rules/signals-effects.md 2.2 KB
- rules/signals-linked-signal.md 2.0 KB
- rules/signals-overview.md 2.3 KB
- rules/signals-resource.md 2.2 KB
- rules/template-async-pipe.md 3.7 KB
- rules/template-avoid-function-calls.md 3.7 KB
- rules/template-control-flow.md 3.0 KB
- rules/template-image-optimization.md 3.3 KB
- rules/template-ng-container.md 3.2 KB
- rules/template-optimize-ngif-ngfor.md 2.9 KB
- rules/testing-zoneless-async.md 2.1 KB
- rules/tooling-cli-generate.md 1.8 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 · 170 lines · 79 tokens per session scan A 20ea68ed2fcf
angular-best-practices is a skill published in the GitHub repository sajeetharan/angular-agent-kit (3 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,617 once invoked, about $0.0004 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 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.