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.
git clone --depth 1 https://github.com/wghglory/ngx-lift-workspaceWrote 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/wghglory/ngx-lift-workspace/angular)<a href="https://agentmods.dev/rules/wghglory/ngx-lift-workspace/angular"><img src="https://agentmods.dev/badge/rules/wghglory/ngx-lift-workspace/angular/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/wghglory/ngx-lift-workspace/angular"><img src="https://agentmods.dev/badge/rules/wghglory/ngx-lift-workspace/angular.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02169 | $0.02169 |
| Opus 5.5 | $0.00868 | $0.00868 |
| Sonnet 5.5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
angular 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 16d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modern Angular Guidelines
Component Architecture
- Standalone Components: All components are standalone by default in modern Angular.
- NEVER add
standalone: trueto@Componentdecorators.
- NEVER add
- Imports: Use
importsarray in@Componentdecorator, not@NgModule. - Change Detection: ALWAYS use
ChangeDetectionStrategy.OnPushfor all components. - Component Lifecycle: Use lifecycle hooks appropriately:
ngOnInit: Component initialization, data fetching setupngAfterViewInit: View-related initialization (ViewChild, ElementRef)ngOnDestroy: Cleanup subscriptions (if any), timers, event listeners- Never put subscription logic in constructor
Signal-Based Development
-
Signal Inputs: Always use signal inputs instead of
@Input()decorators// ✅ Correct name = input<string>(); age = input.required<number>(); // ❌ Wrong @Input() name?: string; @Input() age!: number; -
Signal Outputs: Use
output()instead of@Output()decorators// ✅ Correct userChange = output<User>(); // ❌ Wrong @Output() userChange = new EventEmitter<User>(); -
ViewChild/ViewChildren: Use signal-based view queries
// ✅ Correct fileElement = viewChild.required<ElementRef<HTMLInputElement>>('file'); items = viewChildren(ItemComponent); // ❌ Wrong @ViewChild('file') fileElement!: ElementRef; -
Computed Signals: Use
computed()for derived statefullName = computed(() => `${this.firstName()} ${this.lastName()}`); -
Async Resources (
resourceAsync):- Prefer
resourceAsync()fromngx-liftfor asynchronous data fetching and mutations (replacingcomputedAsyncfor resources). - Provides
value,isLoading,error,status,reload(),execute(), andreset().
// In component: userRef = resourceAsync(() => this.userService.getUser(this.userId())); // In template: @if (userRef.isLoading()) { <cll-spinner /> } @if (userRef.error(); as err) { <cll-alert [error]="err" /> } @if (userRef.value(); as user) { <p>{{ user.name }}</p> } - Prefer
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.
- 16d ago First seen · 253 lines · 2,169 tokens per session scan A 46c463d69230
angular is a cursor rule published in the GitHub repository wghglory/ngx-lift-workspace (7 stars, last pushed yesterday), licensed MIT. It adds 2,169 tokens to every session, about $0.0087 per session on Opus 5.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-10-02.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.