modus-angular-button-group-usage-short

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

A set of Angular coding rules for using Modus buttons inside a Modus button group. The group controls the buttons’ appearance, such as filled, outlined, or borderless styles.

In plain words
What is it for?
Use it when building or reviewing Angular interfaces with ModusButton and ModusButtonGroup, including checks for standalone buttons and all three visual variants.
Why use it?
It prevents button-level defaults from overriding the group’s styling and causing inconsistent-looking controls.

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-button-group-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-button-group-usage-short

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-button-group-usage-short.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-button-group-usage-short)
Your own site
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-button-group-usage-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-button-group-usage-short.svg" alt="Measured on agentmods" height="20"></a>
Per session 362 This file is loaded in full into every session.
When invoked 362 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.00362 $0.00362
Opus 5 $0.00181 $0.00181
Sonnet 5 $0.00072 $0.00072
Haiku 4.5 $0.00036 $0.00036

Measured 3d ago against content hash cc404da352c3, 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-button-group-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 3d 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-button-group-usage-short.mdc · 48 lines

What it actually says

Modus Button Group Usage - Short

Critical pattern to avoid styling conflicts in button groups.

Key Rules

  • No defaults for variant/color in ModusButton - Defaults override button group settings
  • Group controls styling - ModusButtonGroup applies variant/color to all child buttons
  • Don't set variant/color on buttons inside groups - Let the group control them
  • Explicitly set props for standalone buttons - When not in a group, set variant and color
  • Group uses setAttribute after load - DOM manipulation requires no conflicting props
  • Test all three variants - Outlined, filled, and borderless should look distinct

Correct Patterns

// CORRECT - No defaults, allows group to control
readonly color = input<ButtonColor | undefined>();
readonly variant = input<ButtonVariant | undefined>();

// WRONG - Defaults override group settings
readonly color = input<ButtonColor>('primary');
readonly variant = input<ButtonVariant>('filled');
<!-- CORRECT: Group controls all button styling -->
<modus-button-group variant="outlined" color="primary">
  <modus-button>Button 1</modus-button>
  <modus-button>Button 2</modus-button>
</modus-button-group>

<!-- WRONG: Individual button props override group -->
<modus-button-group variant="outlined">
  <modus-button variant="filled">Button</modus-button>
</modus-button-group>

Reference

For detailed patterns and wrapper component implementation, fetch the full rule: modus-angular-button-group-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. 3d ago First seen · 48 lines · 362 tokens per session scan A cc404da352c3

Subscribe to this mod's changes

modus-angular-button-group-usage-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 362 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.