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/100-angular-generalgit 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.00306 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
100-angular-general 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.
What it actually says
Angular General Guidelines
-
Embrace Angular 19+ Features: Use standalone components, signals for state management, and modern template control flow syntax.
-
File Structure: Follow
feature.type.tsnaming pattern (e.g.,hero-list.component.ts,auth.service.ts). -
Single Responsibility: Each file should have one component, service, pipe, or directive. Never combine multiple classes in a single file.
-
Keep Files Small: Aim for less than 350 lines per file. If a component grows beyond this, consider splitting it into smaller components.
-
Extract Templates/Styles: For components with more than 3 lines of template or styles, use separate HTML and CSS files.
-
Change Detection: Use OnPush change detection by default for all components. ALWAYS Prefer signals and computed values for leveraging reactive change detection!
-
Standalone Components: ALWAYS Use standalone components, directives, and pipes.
-
Dependency Injection: Always inject services and dependencies using the
inject()function. -
Naming Conventions:
- Component selectors: Use kebab-case with a custom prefix (e.g.,
app-hero-list) - Directive selectors: Use camelCase (e.g.,
[appHighlight]) - Class names: Use PascalCase (e.g.,
HeroListComponent) - Properties/methods: Use camelCase (e.g.,
selectedHero,getHeroes())
- Component selectors: Use kebab-case with a custom prefix (e.g.,
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 · 28 lines · 0 tokens per session scan A f2babaab0502
100-angular-general 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 306 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.