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/400-angular-directivesgit 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/400-angular-directives)<a href="https://agentmods.dev/rules/jrpribs/smarterstarter/400-angular-directives"><img src="https://agentmods.dev/badge/rules/jrpribs/smarterstarter/400-angular-directives.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.00005 | $0.01106 |
| Opus 5 | $0.00003 | $0.00553 |
| Sonnet 5 | $0.00001 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
400-angular-directives 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 4d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Directives Best Practices
- Standalone Directives: Use standalone directives to avoid NgModule configuration.
@Directive({
selector: '[appHighlight]',
standalone: true
})
export class HighlightDirective {
constructor(private el: ElementRef) {}
@HostListener('mouseenter')
onMouseEnter() {
this.highlight('yellow');
}
@HostListener('mouseleave')
onMouseLeave() {
this.highlight(null);
}
private highlight(color: string | null) {
this.el.nativeElement.style.backgroundColor = color;
}
}
- Directive Inputs: For directives, use signal-based inputs with the new
input()function.
@Directive({
selector: '[appHighlight]',
standalone: true
})
export class HighlightDirective {
highlightColor = input<string>('yellow'); // Default color
constructor(private el: ElementRef) {}
@HostListener('mouseenter')
onMouseEnter() {
this.el.nativeElement.style.backgroundColor = this.highlightColor();
}
@HostListener('mouseleave')
onMouseLeave() {
this.el.nativeElement.style.backgroundColor = null;
}
}
- Prefer @HostListener and @HostBinding: Use decorators for host event binding and property binding rather than host configuration in the directive decorator.
// Prefer this:
@HostBinding('attr.role') role = 'button';
@HostListener('click') onClick() { /* ... */ }
// Instead of:
@Directive({
selector: '[appButton]',
host: {
'[attr.role]': 'role',
'(click)': 'onClick()'
}
})
- Signal Effects in Directives: Use effects to reactively update the DOM when inputs change.
@Directive({
selector: '[appTooltip]',
standalone: true
})
export class TooltipDirective implements OnInit {
tooltipText = input<string>('');
tooltipPosition = input<'top' | 'bottom' | 'left' | 'right'>('top');
constructor(
private el: ElementRef,
private renderer: Renderer2,
private injector: Injector
) {}
ngOnInit() {
// Use effect to update tooltip when inputs change
effect(() => {
const text = this.tooltipText();
const position = this.tooltipPosition();
// Update tooltip with new values
if (this.tooltipElement) {
this.renderer.setProperty(this.tooltipElement, 'textContent', text);
this.updateTooltipPosition(position);
}
}, { injector: this.injector });
}
// Rest of directive implementation
}
- Custom Prefix: Use a custom prefix for directive selectors to avoid conflicts with standard HTML attributes. Don't use the 'ng' prefix which is reserved for Angular.
// Good
selector: '[appHighlight]'
// Avoid
selector: '[highlight]' // Too generic
selector: '[ngHighlight]' // Uses reserved 'ng' prefix
- Selector Naming: Use lowerCamelCase for directive selectors.
// Good
selector: '[appTooltip]'
// Avoid
selector: '[app-tooltip]'
- Directive Composition API: For more complex directives, consider using the newer Directive Composition API to compose multiple behaviors.
@Directive({
selector: '[appEnhancedInput]',
standalone: true,
hostDirectives: [
{
directive: TooltipDirective,
inputs: ['tooltipText', 'tooltipPosition'],
},
{
directive: FocusHighlightDirective,
inputs: ['highlightColor'],
}
]
})
export class EnhancedInputDirective {
// This directive composes other directives without additional code
}
-
Structural Directives: When creating structural directives, prefer the modern control flow directives (@if, @for) for most cases. Only create custom structural directives for truly unique manipulation of the DOM structure.
-
Directive Documentation: Document how to use your directive with JSDoc comments, including all inputs and outputs.
/**
* Directive that highlights an element when hovered.
*
* @example
* <div [appHighlight]="'yellow'">Hover me</div>
*
* @publicApi
*/
@Directive({
selector: '[appHighlight]',
standalone: true
})
export class HighlightDirective {
// implementation
}
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.
- 4d ago First seen · 202 lines · 5 tokens per session scan A a25e59e55751
400-angular-directives is a cursor rule published in the GitHub repository JrPribs/SmarterStarter (2 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 1,106 once invoked, about $0.0000 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 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.