modus-angular-side-navigation-usage

A set of Angular integration rules for using Modus Navbar and Side Navigation components together. Angular is a web framework, and Modus provides the interface components.

In plain words
What is it for?
Use it when connecting a Modus top navigation bar to a side menu in an Angular application, including menu events, positioning, layering, and property binding.
Why use it?
It helps avoid common layout, event-handling, and component-binding mistakes when building this navigation pattern.

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-side-navigation-usage
Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 993 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00993
Opus 5 $0.00000 $0.00496
Sonnet 5 $0.00000 $0.00199
Haiku 4.5 $0.00000 $0.00099

Measured 2d ago against content hash b90938c6d08e, 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-side-navigation-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.

templates/angular/.cursor/rules/modus-angular-side-navigation-usage.mdc · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Modus Navbar + Side Navigation Integration (Angular)

Critical patterns for integrating modus-navbar with modus-side-navigation in Angular applications.

Key Rules

  • Use Angular wrapper components - Use modus-navbar and modus-side-navigation, not raw web components
  • Pass props as native objects - Angular handles binding automatically
  • Listen for mainMenuOpenChange events - Use DOM event listeners on container
  • Position side navigation absolutely - Required for proper layering
  • Set explicit z-index - Ensure side navigation renders above content

DO: Use Angular Wrapper Components

<!-- DO: Use Angular wrapper components -->
<modus-navbar [userCard]="userCardInfo()" [visibility]="{ mainMenu: true, user: true }" />

<modus-side-navigation
  [expanded]="false"
  [collapseOnClickOutside]="true"
  [maxWidth]="'256px'"
  mode="push"
  [targetContent]="'#panel-content'"
/>

DO: Setup Event Listeners in ngAfterViewInit

export class SideNavigationDemoComponent implements AfterViewInit {
  readonly navbarMenuExpanded = signal<boolean>(false);

  constructor(private elementRef: ElementRef) {}

  ngAfterViewInit(): void {
    this.setupNavbarSideNavigationIntegration();
  }

  private setupNavbarSideNavigationIntegration(): void {
    const container = this.elementRef.nativeElement.querySelector('.layout-with-navbar');

    container.addEventListener('mainMenuOpenChange', (event: any) => {
      const sideNav = container.querySelector('modus-wc-side-navigation');

      if (sideNav) {
        sideNav.expanded = event.detail;
        this.navbarMenuExpanded.set(event.detail);
      }
    });

    const sideNav = container.querySelector('modus-wc-side-navigation');
    sideNav?.addEventListener('expandedChange', (event: any) => {
      this.navbarMenuExpanded.set(event.detail);
    });
  }
}

DO: Position Side Navigation Absolutely with Z-Index

.layout-with-navbar {
  box-shadow: rgba(36, 35, 45, 0.3) 1px 0 4px;
  display: flex;
  flex-direction: column;
  height: 100%;
}

.layout-with-navbar .main-content-row {
  display: flex;
  flex: 1;
  overflow: hidden;
  position: relative;
  min-height: 500px;
}

.layout-with-navbar .side-navigation,
.layout-with-navbar modus-side-navigation {
  position: absolute;
  left: 0;
  top: 0;
  height: 100%;
  z-index: 999;
}

.layout-with-navbar .panel-content {
  flex: 1;
  padding: 1.5rem;
  overflow: auto;
  margin-left: 4rem;
}

Read the full file on GitHub · 137 lines

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. 2d ago First seen · 137 lines · 0 tokens per session scan A b90938c6d08e

Subscribe to this mod's changes

modus-angular-side-navigation-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 993 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.