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.
git 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/kubestellar-console)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/kubestellar-console"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/kubestellar-console.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.00626 | $0.00626 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
kubestellar-console 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KubeStellar Console Development Rules
Project Structure
- Frontend: React + TypeScript in
/web/ - Backend: Go (Fiber v2) in root directory
- Build:
cd web && npm run build && npm run lintbefore every commit - Cards: Dashboard card components in
web/src/components/cards/ - Hooks: Data fetching hooks in
web/src/hooks/
Card Development
- All data fetching MUST go through
useCache/useCached*hooks - Always destructure and pass
isDemoDataandisRefreshingtouseCardLoadingState() - Never use demo data during loading:
isDemoFallback && !isLoading - Hook ordering:
useCardLoadingStateAFTER hooks providingisDemoData
Array Safety
- NEVER call
.join(),.map(),.filter(),.forEach(),for...ofon values that might be undefined - Always guard:
(data || []).map(...)or(data || []).join(', ')
No Magic Numbers
- Numeric literals should be named constants, except trivial literals (
0,1,-1) in clear local contexts - Use constants from
lib/constants/(time.ts, network.ts, ui.ts)
Styling
- Tailwind CSS with
cn()utility for merging classNames - Never use raw hex colors — use semantic Tailwind classes (
text-foreground,bg-primary,bg-card) - Status colors:
text-green-400/bg-green-500/10(success),text-yellow-400/bg-yellow-500/10(warning),text-red-400/bg-red-500/10(error),text-cyan-400/bg-cyan-500/10(info) — these map to the design system's semantic status tokens and are the only permitted palette classes
Internationalization
- All user-facing strings use
t()fromreact-i18next - Keys in
web/src/locales/en/JSON files - Never use raw strings for UI text
Go Backend
- Fiber v2 handlers:
func(c *fiber.Ctx) error - Use
fiber.NewError(statusCode, message)for errors - Always
make([]T, 0)notvar x []T(nil → null in JSON) - Use
log/slogfor structured logging - Multi-cluster queries use goroutines + sync.WaitGroup
Cluster Deduplication
- Always use
DeduplicatedClusters()when iterating clusters - Multiple kubeconfig contexts can point to same physical cluster
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 · 49 lines · 626 tokens per session scan A 896be5383f8b
kubestellar-console is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,734 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 626 tokens to every session, about $0.0031 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
vue3-typescript-auto
Vue 3 with TypeScript Standards.
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.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
tailwind-css
Tailwind CSS: utility patterns, design tokens, component extraction.