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.
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs-shortgit 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-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-button-group-usage-solidjs-short.svg" alt="Measured on agentmods" 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 | $0.00237 | $0.00237 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
modus-button-group-usage-solidjs-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 yesterday.
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
95% identical to modus-button-group-usage-react-short — 4 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.
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
- Use conditional prop spreading -
{...(variant && { variant })}to only pass when defined - 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 SolidJS props
- Test all three variants - Outlined, filled, and borderless should look distinct
Reference
For detailed patterns, web component internals, and testing checklist, fetch the full rule: modus-button-group-usage-solidjs
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.
- yesterday First seen · 24 lines · 237 tokens per session scan A 54df8a9fb1ae
modus-button-group-usage-solidjs-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 237 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to modus-button-group-usage-react-short, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
accessibility
Rules for ensuring accessibility in Astro components, including semantic HTML and ARIA attributes.
tailwind-css-styling-rules
在Next.js 14组件中使用Tailwind CSS进行样式设计的规则。.