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/development-workflow-react-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/development-workflow-react-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/development-workflow-react-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.1 | $0.00217 | $0.00217 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
development-workflow-react-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- development-workflow-solidjs-short — 86% identical, 6 lines differ
What it actually says
Development Workflow - Short
Essential linting and quality checks for React + Vite development.
Key Rules
- Run linting commands during development -
npm run lint:allbefore commits - Fix violations before committing - No violations in committed code
- Check inline styles -
npm run lint:stylesto catch inline style violations - Verify design system colors -
npm run lint:colorsfor color compliance - Validate Modus icons -
npm run lint:iconsfor icon usage - Check semantic HTML -
npm run lint:semanticfor HTML compliance - Verify border usage -
npm run lint:bordersfor border compliance
Reference
For detailed linting commands, quality gates, and development workflow patterns, fetch the full rule: development-workflow-react
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 · 24 lines · 217 tokens per session scan A 9a12e783be74
development-workflow-react-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 217 tokens to every session, about $0.0011 per session on Opus 5. 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-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
custom-component
Guide for creating React components using the useProps pattern with Mantine for centralized theme-based styling. Apply when creating or modifying components that need theme integration.
hatch3r-performance-budgets
Core Web Vitals targets, API response-time tables, database query caps, bundle-size limits, and Lighthouse CI enforcement gates.