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 rules/jrpribs/smarterstarter/angular-best-practicesgit clone --depth 1 https://github.com/JrPribs/SmarterStarterWhat 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.00000 | $0.00562 |
| Opus 5 | $0.00000 | $0.00281 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Best Practices
General Guidelines
- Always use Angular's latest syntax.
- Use signals and signal-based input() and output() functions & control flow syntax.
- Always separate component ts, view, & style code into their own files.
Routing Best Practices
- Always use Angular router when navigating between views or showing/hiding significant UI elements.
- Use named router outlets for side panels, dialogs, and other overlay components that need route-based control.
- Lazy load routes files and components that aren't needed immediately on load of the app.
- Use functional resolvers and component input binding in routed components.
Component Input/Output Patterns
- Use signal inputs (input()) and model signals (model()) for component inputs.
- Prefer explicit input declarations over object-based data passing.
- For inputs that can change, use signal inputs to ensure reactivity.
- Use outputs that emit specific data types rather than generic events when possible.
Side Panel Implementation
- Use named router outlets (like 'side-panel') for all side panel components.
- Create a standardized side panel layout with consistent animations and structure.
- Side panels should be self-contained components that get their data from resolvers.
- Use a single "close" mechanism that uses router navigation to close the panel.
State Management
- Use a one-way data flow pattern as outlined in state-architecture.data-flow.md.
- Use resolvers to fetch data for components rather than fetching data directly in components.
- Prefer passing resolved data to components over components fetching their own data.
Resolver Pattern
- Create focused resolvers that handle a single responsibility.
- Use resolvers to prefetch data before component initialization.
- Return null/empty data rather than throwing errors when data is unavailable.
- Handle error states in resolvers, not in components.
Lazy Loading
- Lazy load large components or feature modules that aren't needed immediately.
- Use the loadComponent/loadChildren pattern in routes.
- Apply preloading strategies for important but not immediately needed routes.
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 · 56 lines · 562 tokens per session scan A 1bdd43041547
angular-best-practices is a cursor rule published in the GitHub repository JrPribs/SmarterStarter (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 562 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.