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/reduxWrote 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/redux)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/redux"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/redux.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.02959 | $0.02959 |
| Opus 5 | $0.01479 | $0.01479 |
| Sonnet 5 | $0.00592 | $0.00592 |
| Haiku 4.5 | $0.00296 | $0.00296 |
Grade A, and why
redux scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await axios.get('/api/posts'); How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
redux Best Practices
Redux is our standard for predictable state management. All new Redux code MUST use Redux Toolkit (RTK). RTK simplifies Redux, enforces best practices, and eliminates boilerplate. Do not use vanilla Redux APIs directly.
1. Code Organization and Structure
Organize your Redux logic by feature, using a "slice" approach. This co-locates all related state, actions, and reducers, improving discoverability and maintainability.
1.1. Feature-First Directory Structure
Group all Redux-related files for a specific feature within a single directory.
src/
├── app/
│ ├── store.js // Root store configuration
│ └── hooks.js // Pre-typed Redux hooks (for TS)
└── features/
├── users/
│ ├── usersSlice.js // User slice (reducer, actions)
│ └── UserList.jsx // Component using user slice
└── posts/
├── postsSlice.js // Post slice
└── PostEditor.jsx // Component using post slice
1.2. Single-File Slices
Define your reducer, initial state, and action creators in a single file using createSlice. This is the "ducks" pattern, simplified by RTK.
❌ BAD: Scattered Redux files
// src/features/posts/actions.js
export const addPost = (payload) => ({ type: 'posts/addPost', payload });
// src/features/posts/reducers.js
const postsReducer = (state = [], action) => { /* ... */ };
// src/features/posts/constants.js
const ADD_POST = 'posts/addPost';
✅ GOOD: Co-located slice with createSlice
// src/features/posts/postsSlice.js
import { createSlice, nanoid } from '@reduxjs/toolkit';
const postsSlice = createSlice({
name: 'posts',
initialState: [],
reducers: {
postAdded: {
reducer(state, action) {
state.push(action.payload);
},
prepare(title, content, userId) {
return {
payload: {
id: nanoid(),
title,
content,
user: userId,
date: new Date().toISOString(),
},
};
},
},
// ... other reducers
},
});
export const { postAdded } = postsSlice.actions;
export default postsSlice.reducer;
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 · 393 lines · 2,959 tokens per session scan A 0571b77c056e
redux 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,959 tokens to every session, about $0.0148 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.