Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-appnpx agentmods add rules/julianoczkowski/create-trimble-app/modus-navbar-side-navigation-reactWrote 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-navbar-side-navigation-react)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-navbar-side-navigation-react"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-navbar-side-navigation-react.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.01487 |
| Opus 5 | $0.00000 | $0.00744 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
modus-navbar-side-navigation-react 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus Navbar + Side Navigation Integration
Critical patterns for integrating ModusWcNavbar with ModusWcSideNavigation in React applications.
Key Rules
- Use the ModusNavbar wrapper component - Never use
ModusWcNavbardirectly - Pass props as native React objects - Wrapper handles serialization
- Sync navbar hamburger menu with side navigation - Use
onMainMenuOpenChangecallback - Position side navigation absolutely - Required for proper layering
- Set explicit z-index - Ensure side navigation renders above content
DO: Use ModusNavbar Wrapper Component
The ModusNavbar wrapper component handles prop serialization and event binding correctly.
// DO: Use the wrapper component
import ModusNavbar from "../../components/ModusNavbar";
<ModusNavbar
userCard={userCard}
visibility={{ mainMenu: true, user: true }}
onMainMenuOpenChange={handleNavbarMenuOpenChange}
/>;
DON'T: Use ModusWcNavbar Directly
Direct usage causes prop serialization issues.
// DON'T: Direct usage won't work properly
import { ModusWcNavbar } from "@trimble-oss/moduswebcomponents-react";
<ModusWcNavbar
user-card={JSON.stringify(userCard)} // Won't work!
visibility={JSON.stringify({ mainMenu: true })} // Won't work!
/>;
DO: Sync Navbar with Side Navigation via Ref
Use a ref to directly set the expanded property on the side navigation.
const [navbarMenuExpanded, setNavbarMenuExpanded] = useState(false);
const sideNavRef = useRef<any>(null);
const handleNavbarMenuOpenChange = useCallback((isOpen: boolean) => {
setNavbarMenuExpanded(isOpen);
// Directly set expanded property on the web component
const sideNav = sideNavRef.current;
if (sideNav) {
sideNav.expanded = isOpen;
}
}, []);
<ModusNavbar
onMainMenuOpenChange={handleNavbarMenuOpenChange}
/>
<ModusWcSideNavigation
ref={sideNavRef}
expanded={navbarMenuExpanded}
/>
DON'T: Rely Only on React State
React state alone won't trigger the web component to expand.
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 · 248 lines · 0 tokens per session scan A c81c279d2950
modus-navbar-side-navigation-react 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 1,487 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.
ant-design
Definitive guidelines for building consistent, performant, and maintainable UIs with Ant Design v6.x, focusing on design tokens, layout, and component usage.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
815-reactflow-diagrams
Conventions for narrative @xyflow/react canvases: custom nodes and edges, semantic stroke colors, Cloudflare orange shell grouping, readability inside tinted frames, handles, and verification before merge.
frontend-specialist
Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive. Use with /frontend…
hip-component
You are an expert design system engineer who is well versed in both https://stylexjs.com/ and https://react-spectrum.adobe.com/react-aria/getting-started.html. When implementing components they should follow the same structure as other components in packages/hip-ui/src/components.