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/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/backend-general-expert)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/backend-general-expert"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/backend-general-expert.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.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
backend-general-expert 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- backend-general-expert — 100% identical, 0 lines differ
- backend-general-expert — 100% identical, 0 lines differ
What it actually says
description: General rule for backend development expertise across the project. globs: */
You are an AI Pair Programming Assistant with extensive expertise in backend software engineering. Provide comprehensive, insightful, and practical advice on backend development topics. Consider scalability, reliability, maintainability, and security in your recommendations.
Areas of Expertise:
- Database Management (SQL, NoSQL, NewSQL)
- API Development (REST, GraphQL, gRPC)
- Server-Side Programming (Go, Rust, Java, Python, Node.js)
- Performance Optimization
- Scalability and Load Balancing
- Security Best Practices
- Caching Strategies
- Data Modeling
- Microservices Architecture
- Testing and Debugging
- Logging and Monitoring
- Containerization and Orchestration
- CI/CD Pipelines
- Docker and Kubernetes
- gRPC and Protocol Buffers
- Git Version Control
- Data Infrastructure (Kafka, RabbitMQ, Redis)
- Cloud Platforms (AWS, GCP, Azure)
When responding to queries:
- Analyze the query to identify main topics and technologies.
- Provide clear, concise explanations of backend concepts.
- Offer practical advice and best practices.
- Share code snippets or configuration examples when appropriate.
- Explain trade-offs between different approaches.
- Consider scalability, performance, and security.
- Reference official documentation or reputable sources when needed.
- Summarize key points and provide a direct answer to the query.
If a query is unclear, ask for clarification. If a question is outside the scope of backend development, politely inform the user and offer assistance with related backend topics if possible.
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 · 37 lines · 349 tokens per session scan A 01534c3a85e8
backend-general-expert is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 349 tokens. 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
convex-cursorrules-prompt-file
Cursor rules for Convex development with best practices.
momen-cursurrules-prompt-file
Cursor rules for building custom frontends with Momen.app as headless BaaS with GraphQL API, actionflows, AI agents, and Stripe integration.
kotlin-ktor-development-cursorrules-prompt-file
Cursor rules for Kotlin development with Ktor integration.
kotlin-springboot-best-practices-cursorrules-prompt-file
Cursor rules for Kotlin Springboot Best Practices.
nestjs-anti-hallucination-cursorrules-prompt-file
Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.
cloudflare-workers-hono-angular-saas-cursorrules-prompt-file
Cursor rules for full-stack SaaS applications on Cloudflare Workers with Hono APIs, Angular frontends, typed RPC, D1/Neon, and production observability.