awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdcnpx agentmods add rules/sanjeed5/awesome-cursor-rules-mdc/react-mobxWrote 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/sanjeed5/awesome-cursor-rules-mdc/react-mobx)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/react-mobx"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/react-mobx.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.02993 | $0.02993 |
| Opus 5 | $0.01496 | $0.01496 |
| Sonnet 5 | $0.00599 | $0.00599 |
| Haiku 4.5 | $0.00299 | $0.00299 |
Grade A, and why
react-mobx 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
react-mobx Best Practices
MobX, paired with React, offers a powerful and low-boilerplate approach to state management. By adhering to these guidelines, your team will build predictable, scalable applications ready for React 19 and the React Compiler.
1. Store Design and Organization
Organize your application state into domain-specific stores, composed into a single root store.
1.1. Class-Based Stores with makeObservable
Define each domain area as a class. Use makeObservable in the constructor to explicitly declare observables, computed values, and actions. This is the modern, explicit way to define your reactive state.
❌ BAD: Implicit MobX decorators (legacy)
// src/stores/UserStore.js
import { observable, action, computed } from 'mobx';
class UserStore {
@observable users = [];
@observable isLoading = false;
@computed get activeUsers() {
return this.users.filter(u => u.isActive);
}
@action addUser(user) {
this.users.push(user);
}
}
✅ GOOD: Explicit makeObservable (modern)
// src/stores/UserStore.ts
import { makeObservable, observable, action, computed } from 'mobx';
interface User {
id: string;
name: string;
isActive: boolean;
}
export class UserStore {
users: User[] = [];
isLoading: boolean = false;
constructor() {
makeObservable(this, {
users: observable,
isLoading: observable,
activeUsers: computed,
addUser: action,
fetchUsers: action,
});
}
get activeUsers(): User[] {
return this.users.filter(u => u.isActive);
}
addUser(user: User) {
this.users.push(user);
}
async fetchUsers() {
this.isLoading = true;
// Simulate API call
await new Promise(resolve => setTimeout(resolve, 500));
this.users = [{ id: '1', name: 'Alice', isActive: true }];
this.isLoading = false;
}
}
1.2. Root Store Composition
Create a RootStore that instantiates and holds references to all other stores. This provides a single entry point for your application's state and facilitates inter-store communication.
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 · 429 lines · 2,993 tokens per session scan A 1f788f5e6e5b
react-mobx is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,993 tokens to every session, about $0.0150 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
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
new-component
Workflow for creating new React components.
middleware-auth
Next.js middleware auth — prevents auth logic being placed in middleware instead of route handlers.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
common-fixes
Utility for VAN QA common validation fixes.