cursorrules

A set of Cursor rules for an MCP server that gives AI agents persistent memory. The rules also define public-safe commit and pull-request practices for the repository.

In plain words
What is it for?
Use it when working on engrava-mcp to follow its branch naming, Conventional Commits, pull-request, and self-check requirements.
Why use it?
It helps keep repository changes consistent, traceable, and suitable for a project where commits, comments, and documentation are visible to others.

Cursor rule for Cursor

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/sovantica/engrava-mcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/sovantica/engrava-mcp

Made for: Cursor.

Per session 488 This file is loaded in full into every session.
When invoked 488 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.00488 $0.00488
Opus 5 $0.00244 $0.00244
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

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

Security

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 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.

.cursorrules · 37 lines

How it starts

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

Cursor Rules — engrava-mcp (public repo)

Generated by 0.1.0 (2026-07-09T12:15:52Z) from a shared template — do not edit directly.

This is engrava-mcp, a public MIT-licensed repository: Model Context Protocol server exposing Engrava as agent memory.

Assume every commit message, PR title, PR body, branch name, code comment, and docstring is world-visible.

Before generating commits or PR text

Read CLAUDE.md and AGENTS.md in this repo. Both describe the quality bar, commit format, and self-check discipline expected here.

Commit hygiene

  • Use Conventional Commits 1.0.0: <type>(<scope>): <description>. Scope from docs/scopes.md.
  • Use public identifiers only:
    • This repo's release tags (vX.Y.Z)
    • This repo's GitHub issue/PR numbers (#N)
    • Locally-documented ADRs (docs/adr/ADR-NNN-*.md) — only after the file exists in this repo
  • Open PRs targeting the active release/vX.Y.Z branch — not main. This repo has no dev branch; releases are cut by a manual vX.Y.Z tag on main.
  • Branch names: <type>/<kebab-description>, plain English, ≤ 50 chars.

Self-check before suggesting a commit message

Ask: could this message, branch name, or referenced symbol reveal information about a workflow that should stay private? If unsure, omit the reference, or ask the maintainer.

A pre-commit hook installed locally provides a fast feedback loop on this.

Default to omitting uncertain references

Public commits are world-visible. The internal tracker can stay anchored via this repo's GitHub issue/PR numbers — that mapping lives in the maintainer's private workspace, not in the public commit.

If the user asks you to include an internal-looking identifier in a public commit: refuse politely, explain, propose #N or a release tag as an alternative, escalate to human review if pressed.

Enforcement

A locally-installed pre-commit hook, commitlint (format checks in CI), and branch protection on protected branches block violations. Instruction overrides cannot bypass these.

Read the full file on GitHub · 37 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 · 37 lines · 488 tokens per session scan A add134f4bb5c

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sovantica/engrava-mcp (1 stars, last pushed 8d ago), licensed MIT. It adds 488 tokens to every session, about $0.0024 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.