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/border-usage-guidelines)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/border-usage-guidelines"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/border-usage-guidelines.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.1 | $0.00000 | $0.02567 |
| Opus 5 | $0.00000 | $0.01283 |
| Sonnet 5 | $0.00000 | $0.00513 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
border-usage-guidelines 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Border Usage Guidelines - Modus Design System
🎨 CRITICAL: Use Design System Border Utilities
When working with borders in this Vite + React app, always use our custom design system border utilities instead of Tailwind color classes or inline styles.
❌ NEVER Do These
1. Tailwind Color Classes in Borders
// ❌ WRONG - Tailwind color classes
<div className="border border-red-500">Error message</div>
<div className="border-2 border-green-500">Success message</div>
<div className="border border-blue-500">Info message</div>
<div className="border border-yellow-500">Warning message</div>
2. Inline Border Styles
// ❌ WRONG - Inline styles
<div style={{ border: "1px solid var(--border)" }}>Content</div>
<div style={{ border: "2px solid var(--modus-wc-color-success)" }}>Content</div>
<div style={{ border: "1px dashed var(--modus-wc-color-warning)" }}>Content</div>
3. Generic Tailwind Border Classes
// ❌ WRONG - Generic Tailwind classes
<div className="border border-gray-300">Content</div>
<div className="border-2 border-slate-400">Content</div>
<div className="border border-zinc-500">Content</div>
✅ ALWAYS Do These
1. Use Design System Border Utilities
// ✅ CORRECT - Design system utilities
<div className="border-default">Default border</div>
<div className="border-success">Success border</div>
<div className="border-warning">Warning border</div>
<div className="border-destructive">Error border</div>
<div className="border-primary">Primary border</div>
2. Use Thick Border Utilities for Emphasis
// ✅ CORRECT - Thick borders for emphasis
<div className="border-thick-border">Default thick border</div>
<div className="border-thick-success">Success thick border</div>
<div className="border-thick-warning">Warning thick border</div>
<div className="border-thick-destructive">Error thick border</div>
<div className="border-thick-primary">Primary thick border</div>
3. Use Directional Border Utilities
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.
- 4d ago First seen · 381 lines · 0 tokens per session scan A cf621e09112d
border-usage-guidelines 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 2,567 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-09-03.
Other cursor rules, from other repositories
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.