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/200-angular-components-tsgit clone --depth 1 https://github.com/JrPribs/SmarterStarterWrote 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/rules/jrpribs/smarterstarter/200-angular-components-ts)<a href="https://agentmods.dev/rules/jrpribs/smarterstarter/200-angular-components-ts"><img src="https://agentmods.dev/badge/rules/jrpribs/smarterstarter/200-angular-components-ts.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.00000 | $0.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
200-angular-components-ts 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 3d 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
REQUIRED Angular Component Best Practices
- Use Standalone Components: Mark components as standalone and import their dependencies directly.
@Component({
selector: 'app-hero-detail',
imports: [CommonModule, RouterOutlet, HeroAvatarComponent],
templateUrl: './hero-detail.component.html',
styleUrl: './hero-detail.component.css',
changeDetection: ChangeDetectionStrategy.OnPush
})
export class HeroDetailComponent {
// Component implementation
}
- Signal-Based Inputs: Use the
input()function instead of@Input()decorators for component inputs.
// Instead of:
// @Input() hero: Hero | undefined;
// Use:
hero = input<Hero | undefined>(undefined);
- Two-Way Binding: Use
model()for two-way binding inputs instead of manual input/output pairs.
// Instead of:
// @Input() counter = 0;
// @Output() counterChange = new EventEmitter<number>();
// Use:
counter = model<number>(0);
// To update and emit:
incrementCounter() {
this.counter.update(value => value + 1);
}
- Event Outputs: Use
output()for component events.
// Instead of:
// @Output() deleted = new EventEmitter<Hero>();
// Use:
deleted = output<Hero>();
// To emit:
onDelete(hero: Hero) {
this.deleted.emit(hero);
}
- Computed Values: Use
computed()for derived state instead of getters or methods.
// Instead of:
// get fullName() { return `${this.firstName} ${this.lastName}`; }
// Use:
firstName = signal('');
lastName = signal('');
fullName = computed(() => `${this.firstName()} ${this.lastName()}`);
- Avoid Aliasing Inputs: Avoid aliasing inputs and outputs unless necessary.
// Avoid:
userId = input<string>('', {alias: 'id'});
// Prefer:
userId = input<string>('');
- Initialize Inputs: Always provide default values for inputs or mark them as optional with
?.
// With default value:
hero = input<Hero | null>(null);
// Or mark as optional:
type = input<'primary' | 'secondary'>('primary');
- Local Derivations: Keep component-specific derivations in the component; global derivations in the store.
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.
- 3d ago First seen · 100 lines · 512 tokens per session scan A 1e7c92451c61
200-angular-components-ts 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 512 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.