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/krejcif/magectorWrote 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/krejcif/magector/cursorrules)<a href="https://agentmods.dev/rules/krejcif/magector/cursorrules"><img src="https://agentmods.dev/badge/rules/krejcif/magector/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/krejcif/magector/cursorrules"><img src="https://agentmods.dev/badge/rules/krejcif/magector/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.01441 | $0.01441 |
| Opus 5.5 | $0.00576 | $0.00576 |
| Sonnet 5.5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
cursorrules 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 2mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Development Rules with Magector
You are an expert Magento 2 developer with access to the Magector semantic code search tool via MCP.
Primary Rule: Use Magector First
When looking for Magento code, ALWAYS use the magector MCP tools BEFORE reading files manually:
- Semantic questions ("how to...", "where is..."): Use
magento_search - Specific classes: Use
magento_find_class - XML configurations: Use
magento_find_config - Templates: Use
magento_find_template - Plugins: Use
magento_find_plugin - Observers: Use
magento_find_observer - API endpoints: Use
magento_find_api - GraphQL: Use
magento_find_graphql - Diff risk analysis: Use
magento_analyze_diffto assess commit or staged change risk - Code complexity: Use
magento_complexityto find complex hotspots in modules
Query Formulation Best Practices
Write queries as natural language questions to a Magento expert:
Effective Query Patterns
| Intent | Query Example |
|---|---|
| Find price logic | "product price calculation tier prices" |
| Find cart code | "add product to cart programmatically" |
| Find checkout flow | "checkout totals collector calculate" |
| Find auth code | "customer login authentication session" |
| Find plugin examples | "plugin before after around save repository" |
| Find observer examples | "observer event sales_order_place_after" |
| Find API endpoints | "webapi rest endpoint products" |
| Find GraphQL | "graphql resolver products query mutation" |
| Find cron jobs | "cron job catalog indexer schedule" |
| Find admin grid | "adminhtml grid ui component listing" |
Query Tips
- Be specific - "product price calculation" not just "price"
- Include concepts - "controller execute action" not just "controller"
- Name the pattern - "plugin before save" not just "plugin"
- Mention file types - "di.xml preference" for config files
Interpreting Results
When Magector returns results, analyze:
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.
- 2mo ago First seen · 190 lines · 1,441 tokens per session scan A e57d82119c6a
cursorrules is a cursor rule published in the GitHub repository krejcif/magector (20 stars, last pushed 11d ago), licensed MIT. It adds 1,441 tokens to every session, about $0.0058 per session on Opus 5.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-30.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).