modus-angular-modal-usage

A set of Angular rules for opening and closing Modus modal dialogs, which are pop-up windows that temporarily focus the user on a task. It uses the browser's native dialog API and the modal element's ID.

In plain words
What is it for?
Use it to wire buttons and handlers to Modus modals, show a dialog, close it, and place content in its header, body, and footer areas.
Why use it?
It gives developers a consistent way to control the modal instead of relying on uncertain component behavior. This makes opening and closing actions explicit in the Angular code.

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-modal-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 850 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.00850
Opus 5 $0.00000 $0.00425
Sonnet 5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

Measured 2d ago against content hash 36e77899a83e, 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-modal-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-modal-usage.mdc · 116 lines

How it starts

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

Comprehensive rules for opening and closing Modus modals in Angular applications.

CORRECT: How to Open/Close Modals

Pattern: Use document.getElementById() with HTMLDialogElement

The Modus modal component creates an HTML <dialog> element with the modalId as its id attribute. Always use the native HTMLDialogElement API to open/close modals.

openModal(): void {
  const dialog = document.getElementById('modal-id') as HTMLDialogElement | null;
  if (dialog && typeof dialog.showModal === 'function') {
    dialog.showModal();
  }
}

closeModal(): void {
  const dialog = document.getElementById('modal-id') as HTMLDialogElement | null;
  if (dialog && typeof dialog.close === 'function') {
    dialog.close();
  }
}

Template Usage

<modus-button color="primary" (buttonClick)="openModal()">Open Modal</modus-button>
<modus-modal modalId="modal-id" [showClose]="true">
  <h3 slot="header">Modal Title</h3>
  <div slot="content">
    <p>Modal content here</p>
  </div>
  <div slot="footer">
    <modus-button color="secondary" (buttonClick)="closeModal()">Close</modus-button>
  </div>
</modus-modal>

WRONG: Common Mistakes

DON'T Use querySelector with Web Component Selector

// WRONG: This doesn't work
openModal(): void {
  const modal = document.querySelector('modus-wc-modal[modal-id="modal-id"]') as any;
  if (modal) {
    modal.open(); // Web component doesn't have an open() method
  }
}

DON'T Use Template References on Wrapper Component

// WRONG: Can't directly call methods on Angular wrapper
@ViewChild(ModusModalComponent) modal!: ModusModalComponent;

openModal(): void {
  this.modal.open(); // Method doesn't exist
}

Best Practices

1. Always Use getElementById with ModalId

openModal(modalId: string): void {
  const dialog = document.getElementById(modalId) as HTMLDialogElement | null;
  if (dialog && typeof dialog.showModal === 'function') {
    dialog.showModal();
  }
}

Read the full file on GitHub · 116 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 · 116 lines · 0 tokens per session scan A 36e77899a83e

Subscribe to this mod's changes

modus-angular-modal-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 850 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.