modus-button-group-usage-solidjs

modus-button-group-usage-solidjs is a cursor rule for Cursor from julianoczkowski/create-trimble-app. It costs 0 tokens per session (906 once invoked), scanned A, a copy of modus-angular-button-group-usage, MIT.

Guidance for making Modus buttons inherit styling from a Modus button group in SolidJS.

In plain words
What is it for?
Use it when implementing button wrappers, grouped variants, inherited colors, and standalone buttons.
Why use it?
It fixes the problem where explicit button defaults make every button look the same despite different group settings.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when implementing button wrappers, grouped variants, inherited colors, and standalone buttons.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs
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.

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

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs/github.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs)
Your own site
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for modus-button-group-usage-solidjs

Your own site · 80×15
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 906 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod 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.1 $0.00000 $0.00906
Opus 5 $0.00000 $0.00453
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00091

Measured 5d ago against content hash 99e1ae55fb9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

modus-button-group-usage-solidjs 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 5d 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.

Origin

This is a copy

83% identical to modus-angular-button-group-usage — 230 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

templates/solidjs/.cursor/rules/modus-button-group-usage-solidjs.mdc · 118 lines

How it starts

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

Modus Button Group Usage

Critical patterns for using ModusButton components inside ModusButtonGroup.

The Problem

When ModusButton has default values for variant and color, these explicit values override the ModusButtonGroup's settings. This causes all buttons to look the same regardless of the group's variant prop.

Root Cause

The modus-wc-button-group web component uses setAttribute() to apply its variant and color to child buttons after they load. If SolidJS buttons have explicit defaults, they override the group's settings.

Correct Pattern

ModusButton Component

Do NOT set defaults for variant or color in the ModusButton wrapper:

// CORRECT - No defaults, allows inheritance from button group
export default function ModusButton({
  color, // undefined by default
  variant, // undefined by default
  size = "md",
  // ...other props
}: ModusButtonProps) {
  return (
    <ModusWcButton
      {...(color && { color })} // Only pass if defined
      {...(variant && { variant })} // Only pass if defined
      size={size}
      // ...other props
    >
      {children}
    </ModusWcButton>
  );
}
// WRONG - Defaults override button group settings
export default function ModusButton({
  color = "primary", // BAD: Will override group's color
  variant = "filled", // BAD: Will override group's variant
  // ...
}: ModusButtonProps) {
  // ...
}

Using ModusButton Standalone

When using ModusButton outside a button group, explicitly set the props you need:

// Standalone button - explicitly set variant and color
<ModusButton variant="filled" color="primary">
  Click Me
</ModusButton>

Using ModusButton in a Button Group

When inside a ModusButtonGroup, do NOT set variant/color on individual buttons:

// CORRECT - Group controls all button styling
<ModusButtonGroup variant="outlined" color="primary">
  <ModusButton>Button 1</ModusButton>
  <ModusButton>Button 2</ModusButton>
  <ModusButton>Button 3</ModusButton>
</ModusButtonGroup>

// WRONG - Individual button props override group settings
<ModusButtonGroup variant="outlined" color="primary">
  <ModusButton variant="filled">Button 1</ModusButton>  // BAD
  <ModusButton color="danger">Button 2</ModusButton>    // BAD
</ModusButtonGroup>

Read the full file on GitHub · 118 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. 5d ago First seen · 118 lines · 0 tokens per session scan A 99e1ae55fb9f

Subscribe to this mod's changes

modus-button-group-usage-solidjs is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 906 tokens. A static security scan graded it A with 0 findings. It is 83% identical to modus-angular-button-group-usage, differing in 230 lines, and is treated as a copy.