modus-angular-navbar-usage-short

modus-angular-navbar-usage-short is a cursor rule for Cursor from julianoczkowski/create-trimble-app. It costs 352 tokens per session, scanned A, original, MIT.

A short set of rules for connecting the Modus Navbar component to an Angular application. It covers search expansion, visible buttons, user details, and application state.

In plain words
What is it for?
Use it when adding a Modus navbar, wiring search and menu controls, or tracking their open and closed states with Angular signals.
Why use it?
It helps avoid a navbar that does not open search, hides buttons unexpectedly, or handles events with the wrong data type.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-navbar-usage-short
Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Wrote 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.

agentmods badge for modus-angular-navbar-usage-short

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-navbar-usage-short.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-navbar-usage-short)
Your own site
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-navbar-usage-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-navbar-usage-short.svg" alt="Measured on agentmods" height="20"></a>
Per session 352 This file is loaded in full into every session.
When invoked 352 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00352 $0.00352
Opus 5 $0.00176 $0.00176
Sonnet 5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 4d ago against content hash 816503c94c35, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

modus-angular-navbar-usage-short 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.

templates/angular/.cursor/rules/modus-angular-navbar-usage-short.mdc · 50 lines

What it actually says

Modus Navbar Usage - Short

Critical patterns for Modus Navbar component in Angular.

Key Rules

  • Set both search and searchInput in visibility - Required for search expansion
  • Use signals for navbar state - Track searchInputOpen, menuOpen states
  • Two-way bind search and menu states - Bind property and handle event
  • Explicitly set button visibility - Buttons default to hidden except user
  • Always provide userCard - Required input for navbar
  • Handle correct event types - Clicks = MouseEvent | KeyboardEvent, state changes = boolean

Search Expansion Pattern

<modus-navbar
  [userCard]="userCard"
  [visibility]="{ user: true, search: true, searchInput: true }"
  [searchInputOpen]="searchInputOpen()"
  (searchClick)="searchInputOpen.set(!searchInputOpen())"
  (searchInputOpenChange)="searchInputOpen.set($event)"
/>

State Management

readonly searchInputOpen = signal<boolean>(false);
readonly mainMenuOpen = signal<boolean>(false);

handleSearchClick(event: MouseEvent | KeyboardEvent): void {
  this.searchInputOpen.set(!this.searchInputOpen());
}

handleMainMenuOpenChange(event: boolean): void {
  this.mainMenuOpen.set(event);
}

Reference

For detailed patterns and event handling, fetch the full rule: modus-angular-navbar-usage

Changes

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.

  1. 4d ago First seen · 50 lines · 352 tokens per session scan A 816503c94c35

Subscribe to this mod's changes

modus-angular-navbar-usage-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 352 tokens to every session, about $0.0018 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.