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.
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWrote 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.
[](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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.
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>
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.
- 5d ago First seen · 118 lines · 0 tokens per session scan A 99e1ae55fb9f
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.
Other cursor rules, from other repositories
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
hatch3r-theming
Theming, dark mode, and color system conventions for the project.
design-ux
Accessibility and design-system conventions for the web dashboard and marketing site.