PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/patrickjs/awesome-cursorrules/semiotic-react-dataviz-cursorrules-prompt-filegit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/semiotic-react-dataviz-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/semiotic-react-dataviz-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/semiotic-react-dataviz-cursorrules-prompt-file.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.07632 | $0.07632 |
| Opus 5 | $0.03816 | $0.03816 |
| Sonnet 5 | $0.01526 | $0.01526 |
| Haiku 4.5 | $0.00763 | $0.00763 |
Grade A, and why
semiotic-react-dataviz-cursorrules-prompt-file 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 2d 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:
- semiotic — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semiotic — AI Assistant Guide
Quick Start
- Install:
npm install semiotic - Import:
semiotic,semiotic/xy,semiotic/ordinal,semiotic/network,semiotic/geo,semiotic/realtime,semiotic/ai,semiotic/data,semiotic/server - CLI:
npx semiotic-ai [--schema|--compact|--examples|--doctor] - MCP:
npx semiotic-mcp - Every HOC has a built-in error boundary (never blanks the page) and dev-mode validation warnings
Architecture
- HOC Charts: Simple props, sensible defaults. Stream Frames: Full control.
- Always use HOC charts (
ForceDirectedGraph,SankeyDiagram,LineChart,RealtimeLineChart,ChoroplethMap, etc.) unless you need sophisticated control they don't expose. Stream Frames (StreamNetworkFrame,StreamXYFrame,StreamOrdinalFrame,StreamGeoFrame) are low-level escape hatches — they accept rawRealtimeNode/RealtimeEdgewrappers in callbacks, not your data objects directly. - Every HOC accepts
framePropsto pass through. TypeScriptstrict: true.
Common Props (all HOCs)
title, width (600), height (400), responsiveWidth, responsiveHeight, margin, className, enableHover (true), tooltip (boolean | (datum) => ReactNode | config object), showLegend, showGrid (false), frameProps, onObservation (callback, see below), chartId, loading (false), emptyContent, legendInteraction ("none"|"highlight"|"isolate"), legendPosition ("right"|"left"|"top"|"bottom", default "right"), emphasis ("primary"|"secondary")
tooltip
tooltip accepts: true (default tooltip), false (disabled), a function (datum: Record<string, any>) => ReactNode, or a config { fields?: string[], title?: accessor, format?: fn, style?: CSSProperties }. The function form receives your raw data object directly.
onObservation
onObservation receives a ChartObservation with type and event-specific fields:
- hover:
{ type: "hover", datum: <your data>, x, y, timestamp, chartType, chartId } - hover-end:
{ type: "hover-end", timestamp, chartType, chartId } - click:
{ type: "click", datum: <your data>, x, y, timestamp, chartType, chartId } - brush:
{ type: "brush", extent: { x: [min, max], y: [min, max] }, timestamp, chartType } - selection:
{ type: "selection", selection: { name, fields }, timestamp, chartType }
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.
- 2d ago First seen · 342 lines · 7,632 tokens per session scan A 06c53daa1252
semiotic-react-dataviz-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 7,632 tokens to every session, about $0.0382 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
react
React and Next.js component conventions.
testing
Testing conventions for Vitest and React Testing Library -- the agent pulls this in when writing or modifying tests.
tanstack-query
TanStack Query / React Query: query keys, mutations, caching, optimistic updates.
react
React: hooks, composition, performance patterns.
t3-stack
T3 Stack: tRPC + Prisma + NextAuth integration patterns.
expo
Expo/React Native: native modules, navigation, platform-specific code.