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
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/sanjeed5/awesome-cursor-rules-mdcWrote 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/mlx)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/mlx"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/mlx.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.02514 | $0.02514 |
| Opus 5 | $0.01257 | $0.01257 |
| Sonnet 5 | $0.00503 | $0.00503 |
| Haiku 4.5 | $0.00251 | $0.00251 |
Grade A, and why
mlx 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 3d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mlx Best Practices
MLX is Apple's high-performance array framework for numerical computing and AI on Apple Silicon. Adhering to these guidelines ensures your MLX code is efficient, maintainable, and integrates seamlessly with Apple's ML ecosystem.
1. Code Organization and Structure
Organize your MLX projects into logical, reusable modules. Mirror the structure of official Apple examples (e.g., corenet MLX examples) for clarity and maintainability.
1.1 Modularize Components
Separate concerns into dedicated files: data loading, model definition, training loops, and utility functions.
❌ BAD: Monolithic Script
# train.py
import mlx.core as mx
import mlx.nn as nn
# ... data loading, model definition, training loop all in one file ...
✅ GOOD: Modular Structure
my_project/
├── data/
│ └── mnist_loader.py
├── models/
│ └── simple_cnn.py
├── config/
│ └── train_config.yaml
├── utils/
│ └── metrics.py
└── train.py
# models/simple_cnn.py
import mlx.core as mx
import mlx.nn as nn
class SimpleCNN(nn.Module):
def __init__(self, num_classes: int):
super().__init__()
self.conv1 = nn.Conv2d(1, 32, kernel_size=3, padding=1)
self.relu1 = nn.ReLU()
self.pool1 = nn.MaxPool2d(kernel_size=2, stride=2)
self.linear = nn.Linear(32 * 14 * 14, num_classes)
def __call__(self, x: mx.array) -> mx.array:
x = self.conv1(x)
x = self.relu1(x)
x = self.pool1(x)
x = x.reshape(x.shape[0], -1) # Flatten
return self.linear(x)
# train.py
from data.mnist_loader import load_mnist_data
from models.simple_cnn import SimpleCNN
# ... training logic ...
1.2 Externalize Configuration
Store training parameters, model hyperparameters, and dataset paths in version-controlled YAML or JSON files.
❌ BAD: Hardcoded Parameters
# train.py
learning_rate = 0.001
batch_size = 32
num_epochs = 10
model = SimpleCNN(num_classes=10)
✅ GOOD: Config-Driven
# config/train_config.yaml
training:
learning_rate: 0.001
batch_size: 32
num_epochs: 10
model:
name: SimpleCNN
num_classes: 10
data:
path: "./data/mnist"
# train.py
import yaml
from models.simple_cnn import SimpleCNN
with open("config/train_config.yaml", "r") as f:
config = yaml.safe_load(f)
model = SimpleCNN(num_classes=config["model"]["num_classes"])
# ... use config["training"]["learning_rate"] etc.
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.
- 3d ago First seen · 302 lines · 2,514 tokens per session scan A 3722f88b795c
mlx 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,514 tokens to every session, about $0.0126 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
tensorflow
TensorFlow: Keras, model training, production deployment.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.