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-modal-implementation-reactgit 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-modal-implementation-react)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-modal-implementation-react"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-modal-implementation-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 | $0.00000 | $0.05307 |
| Opus 5 | $0.00000 | $0.02653 |
| Sonnet 5 | $0.00000 | $0.01061 |
| Haiku 4.5 | $0.00000 | $0.00531 |
Grade A, and why
modus-modal-implementation-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 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.
How it starts
The opening of the file, as written. The whole thing — 832 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ModusWcModal Implementation in React
🚨 CRITICAL: Modal Method Access Issue
Problem: The ModusWcModal component's showModal() and close() methods are not directly available on the component reference in React.
Root Cause: Modus Web Components use shadow DOM, and the modal methods are on the inner native <dialog> element, not the component itself.
Official Documentation: According to the official Modus documentation, modals are controlled with direct method calls (showModal() and close()) on the modal element, not through React state management.
❌ Common Anti-Patterns
❌ Direct Method Access (Won't Work)
// ❌ WRONG: Direct method access on component
function ModalComponent() {
const modalRef = useRef<ModusWcModal>(null);
const openModal = () => {
if (modalRef.current) {
modalRef.current.showModal(); // ❌ This won't work
}
};
const closeModal = () => {
if (modalRef.current) {
modalRef.current.close(); // ❌ This won't work
}
};
return (
<div>
<button onClick={openModal}>Open Modal</button>
<ModusWcModal ref={modalRef}>
<div slot="header">Modal Header</div>
<div slot="body">Modal Body</div>
<div slot="footer">
<button onClick={closeModal}>Close</button>
</div>
</ModusWcModal>
</div>
);
}
❌ Trying to Control Modal State from React
// ❌ WRONG: Trying to control modal state from React
function ModalComponent() {
const [isOpen, setIsOpen] = useState(false);
return (
<ModusWcModal
open={isOpen} // ❌ This won't work as expected
onClose={() => setIsOpen(false)}
>
<div slot="header">Modal Header</div>
<div slot="body">Modal Body</div>
</ModusWcModal>
);
}
❌ Using useEffect to Control Modal State (Critical Anti-Pattern)
// ❌ WRONG: Using useEffect to control modal state
function ModusModal({ isOpen, onClose, ...props }) {
const modalRef = useRef<HTMLModusWcModalElement>(null);
// ❌ CRITICAL ANTI-PATTERN: Don't control modal state from React
useEffect(() => {
const modal = modalRef.current;
if (modal) {
if (isOpen) {
const dialogElement = modal.querySelector("dialog");
if (dialogElement) {
dialogElement.showModal();
}
} else {
const dialogElement = modal.querySelector("dialog");
if (dialogElement) {
dialogElement.close();
}
}
}
}, [isOpen]); // ❌ This violates the official pattern
return <ModusWcModal ref={modalRef} {...props} />;
}
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 · 832 lines · 0 tokens per session scan A 46601fb4c419
modus-modal-implementation-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 5,307 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
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-react-router_routing
TanStack Router: Routing.
nextjs
ContextOS rules for nextjs.
react
React 开发规范 - Actions/use()/Server Actions/useOptimistic/并发特性.
react-prefer-shadcn-components
Preferir componentes shadcn/ui sobre alternativas custom o de terceros.