agentmods.dev

000-core-rulesync-enhanced

A project-wide rules file for standardizing service interfaces and applying prioritization guidance. Its 80/20 rule means focusing on the few factors likely to have the largest impact.

In plain words
What is it for?
Use it to identify the main risks or drivers and rank proposed work by impact compared with effort.
Why use it?
It gives the coding agent consistent instructions about priorities and recommendations across the project.

Cursor rule for Cursor

2 1y ago A scan 1,016 tokens original MIT
View the source file hamzaamjad/cursor-rules
Install

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.

agentmods
npx agentmods add rules/hamzaamjad/cursor-rules/000-core-rulesync-enhanced
Clone the repo
git clone --depth 1 https://github.com/hamzaamjad/cursor-rules

Made for: Cursor.

Per session 1,016 This file is loaded in full into every session.
When invoked 1,016 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01016 $0.01016
Opus 5 $0.00508 $0.00508
Sonnet 5 $0.00203 $0.00203
Haiku 4.5 $0.00102 $0.00102

Measured 2d ago against content hash 13254d29a983, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

000-core-rulesync-enhanced 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 2d 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.

.cursor/rules/000-core-rulesync-enhanced.mdc · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

---\ndescription: "Enhanced rulesync with profile-based aggregation"\nglobs:\n - **/*\nalwaysApply: true\npriority: 999\nversion: "2.0.0"\ntags:\n - core\n - standards\n - rulesync\n - enhanced\ncreated: "2025-07-14T06:18:19.120232"\nlast_modified: "2025-07-14T06:18:19.120233"\n---\n\n# mirror-project - Cursor Rules\nGenerated on: 2025-07-14T06:18:19.120214\nProfile: mirror-project v1.0.0\nSelected rules: 2\n\n## 000-core/002-pareto-prioritization.mdc\n# 80-20-prioritization.mdc

  • Purpose: To guide AI assistants and developers in focusing efforts and recommendations on the most impactful elements, aligning with the Pareto principle (80/20 rule). Ensure resources are directed towards tasks yielding the highest value or mitigating the most significant risks. Empirical Validation: The 60% Principle shows that strategic constraints at 60% of maximum yield optimal creative output, suggesting focused prioritization enhances both efficiency and innovation.
  • Requirements:
    • Identify and highlight the top 1-3 drivers or risks associated with a problem or proposal.
    • Rank recommendations explicitly based on estimated Return on Investment (ROI) or impact/effort ratio.
    • Quantitative ROI Calculation:
      • Time ROI: (Hours Saved × Frequency) / Implementation Hours
      • Risk ROI: (Potential Loss Prevented × Probability) / Mitigation Cost
      • Performance ROI: (% Improvement × Business Value) / Development Cost
      • Target minimum ROI: 3:1 for immediate implementation
    • Clearly state the criteria or heuristics used for ranking (e.g., estimated time saved, revenue generated, risk reduction level, user impact).
    • Avoid detailed exploration or implementation of low-impact features or optimizations unless specifically requested.
    • Cognitive Load Distribution: Ensure AI handles 60-70% of mechanistic processing, leaving 30-40% for human strategic oversight.
  • Validation:
    • Check: Does the output explicitly list top drivers/risks separately or at the beginning?
    • Check: Are recommendations presented in a ranked or prioritized list?
    • Check: Is the basis for ranking (ROI, impact/effort, etc.) mentioned?
    • Check: Does the depth of detail correspond to the priority of the item?
  • Examples:
    • Scenario: Proposing database optimizations.
      • Weak: "We could optimize the users table index and rewrite the orders query."
      • Improved: "1. Optimize orders query (High ROI): Addresses primary source of user-reported latency (est. 80% of slowdown). Effort: Medium. 2. Optimize users table index (Low ROI): Minor performance gain for admin view. Effort: Low. Priority is the orders query."
    • Scenario: Analyzing technical debt.
      • Weak: "There's tech debt in auth and logging."
      • Improved: "Top Risk: Outdated auth library (High - Security Vulnerability). Recommendation (Highest ROI): Upgrade auth library immediately (Effort: High). Other Issue: Inconsistent logging format (Medium - Hinders Debugging). Recommendation (Medium ROI): Refactor logging module next quarter (Effort: Medium)."
  • Changes: Added explicit requirements for stating ranking criteria, refined purpose, provided concrete validation checks, and added comparative examples for different scenarios.
  • Source References: .cursor/rules/80-20-prioritization.mdc; Stack Overflow: Estimating ROI for Tech Debt; LinkedIn: Measure ROI of Refactoring\n\n## 400-patterns/431-api-design-guidelines.mdc\n# api-design-guidelines

Purpose: Standardize service interfaces for consistency and usability.

  • Version your API in the URL or headers (e.g. /v1/users).
  • Use consistent pagination (limit/offset or cursors).

Read the full file on GitHub · 35 lines

Changes

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.

  1. 2d ago First seen · 35 lines · 1,016 tokens per session scan A 13254d29a983

Subscribe to this mod's changes

000-core-rulesync-enhanced is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 1,016 tokens to every session, about $0.0051 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-08-31.

Related

Other cursor rules, from other repositories

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

cli-error-handling

CLI command error handling patterns.

prisma/orm · 0 tokens

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.

prisma/orm · 0 tokens

control-plane-descriptors

Control plane descriptor and instance implementation patterns.

prisma/orm · 0 tokens

family-instance-domain-actions

Family instance domain action implementation patterns.

prisma/orm · 0 tokens