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/julianoczkowski/create-trimble-app/modus-angular-navbar-usagegit clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWhat 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.00893 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
modus-angular-navbar-usage 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navbar Usage Rules
Comprehensive guide for using the Modus Navbar component in Angular, covering search expansion, button visibility, event handling, and state management.
CRITICAL: Search Input Expansion
DO: Set Both search and searchInput in Visibility
For search to expand, you MUST set both visibility flags:
<modus-navbar
[userCard]="userCard"
[visibility]="{ user: true, search: true, searchInput: true }"
[searchInputOpen]="searchInputOpen()"
(searchClick)="handleSearchClick($event)"
(searchInputOpenChange)="handleSearchInputOpenChange($event)"
/>
DO: Two-Way Bind Search State
readonly searchInputOpen = signal<boolean>(false);
handleSearchClick(event: MouseEvent | KeyboardEvent): void {
this.searchInputOpen.set(!this.searchInputOpen());
}
handleSearchInputOpenChange(event: boolean): void {
if (this.searchInputOpen() !== event) {
this.searchInputOpen.set(event);
}
}
Button Visibility Patterns
DO: Set Visibility for Each Button
<modus-navbar
[userCard]="userCard"
[visibility]="{
user: true,
search: true,
searchInput: true,
help: true,
apps: true,
notifications: true,
mainMenu: true
}"
/>
Default visibility settings:
readonly visibility = input<INavbarVisibility | undefined>({
ai: false,
apps: false,
help: false,
mainMenu: false,
notifications: false,
search: false,
searchInput: false,
user: true,
});
Event Handling Patterns
DO: Handle Events with Correct Types
handleSearchClick(event: MouseEvent | KeyboardEvent): void {
this.searchInputOpen.set(!this.searchInputOpen());
}
handleMainMenuOpenChange(event: boolean): void {
this.mainMenuOpen.set(event);
}
handleSearchChange(event: { value: string }): void {
this.lastSearch.set(event.value);
}
State Management Patterns
DO: Use Signals for Navbar State
export class NavbarComponent {
readonly searchInputOpen = signal<boolean>(false);
readonly lastSearch = signal<string>('');
readonly mainMenuOpen = signal<boolean>(false);
readonly notificationsMenuOpen = signal<boolean>(false);
readonly appsMenuOpen = signal<boolean>(false);
}
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 · 147 lines · 0 tokens per session scan A 78614c899768
modus-angular-navbar-usage is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 893 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.