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/pyside)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/pyside"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/pyside.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.03007 | $0.03007 |
| Opus 5 | $0.01503 | $0.01503 |
| Sonnet 5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
pyside 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PySide6 Best Practices
This guide outlines the essential best practices for developing robust, maintainable, and modern PySide6 applications. Adhere to these principles to ensure high-quality, performant, and future-proof code.
1. Code Organization & UI Generation
Principle: Strictly separate UI definition from application logic. Leverage Qt Designer for visual UI creation and pyside6-uic for generating Python UI classes.
Rule: Always design your user interfaces visually in Qt Designer. Convert the .ui files to Python classes using pyside6-uic, then import and compose these generated UI classes within a dedicated Python controller class. Never manually modify the generated ui_*.py files.
❌ BAD: Hand-coding complex UI layouts directly in Python, or modifying generated UI files.
# main.py (Bad: Hand-coding UI directly)
from PySide6.QtWidgets import QApplication, QMainWindow, QPushButton, QVBoxLayout, QWidget
class MainWindow(QMainWindow):
def __init__(self):
super().__init__()
self.setWindowTitle("Bad UI Design - Hand-coded")
central_widget = QWidget()
self.setCentralWidget(central_widget)
layout = QVBoxLayout(central_widget)
self.button = QPushButton("Click Me")
layout.addWidget(self.button)
self.button.clicked.connect(self.on_button_clicked)
def on_button_clicked(self):
print("Button clicked!")
✅ GOOD: Use pyside6-uic generated UI classes composed in a controller.
# 1. Design 'my_app.ui' in Qt Designer (e.g., a QMainWindow with a QPushButton named 'myButton').
# 2. Run: pyside6-uic my_app.ui -o ui_my_app.py
#
# ui_my_app.py (Generated file - DO NOT MODIFY MANUALLY)
# from PySide6 import QtCore, QtWidgets
# class Ui_MainWindow(object):
# def setupUi(self, MainWindow):
# MainWindow.setObjectName("MainWindow")
# self.centralwidget = QtWidgets.QWidget(MainWindow)
# self.myButton = QtWidgets.QPushButton(self.centralwidget)
# self.myButton.setObjectName("myButton")
# MainWindow.setCentralWidget(self.centralwidget)
# self.retranslateUi(MainWindow)
# QtCore.QMetaObject.connectSlotsByName(MainWindow)
# def retranslateUi(self, MainWindow):
# _translate = QtCore.QCoreApplication.translate
# MainWindow.setWindowTitle(_translate("MainWindow", "My App"))
# self.myButton.setText(_translate("MainWindow", "Click Me"))
# main.py (Controller class)
from PySide6.QtWidgets import QApplication, QMainWindow
from ui_my_app import Ui_MainWindow # Import the generated UI class
import sys
class MainWindow(QMainWindow):
def __init__(self):
super().__init__()
self.ui = Ui_MainWindow()
self.ui.setupUi(self) # Initialize the UI from the generated class
self.setWindowTitle("Good UI Design - Composed") # Override title if needed
# Connect signals AFTER setupUi
self.ui.myButton.clicked.connect(self._on_button_clicked)
def _on_button_clicked(self):
print("Button clicked from composed UI!")
if __name__ == "__main__":
app = QApplication(sys.argv)
window = MainWindow()
window.show()
sys.exit(app.exec())
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 · 369 lines · 3,007 tokens per session scan A 336c495a19ce
pyside 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 3,007 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
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
cursorrules
You are a senior TypeScript developer working on a Next.js 16 application.
react-vite-tanstack
You are an expert in TypeScript, Node.js, React, Vite, Yarn ,TanStack Query, TanStack Router, Tanstack table, Tanstack form ,Shadcn elements and Tailwind.
gradio
A set of coding rules for using Gradio, a Python tool for building interfaces around machine-learning applications. The rules cover its client library, API calls, streaming results, errors, jobs, deployment, and security considerations.
element-file-structure-rules
Rules for maintaining a consistent file structure within individual element directories.
fasthtml
The main file for the project is mainsqlite.py It uses MonsterUI for styling. MonsterUI is a python first UI component library that primarily leverages FrankenUI and Tailwind, but also includes headers and functionality form DaisyUI, Katex, HighlightJS, and others.