cursorrules

Project-specific rules for GoldenMatch Extensions, a codebase that connects a Rust bridge, a PostgreSQL extension, and DuckDB functions for a Python record-matching toolkit. It also describes the project's branch, merge, environment, and account procedures.

In plain words
What is it for?
Use it when working on GoldenMatch Extensions, especially when creating branches, preparing pull requests, running the project in the stated Windows and Bash setup, or publishing changes with the correct GitHub account.
Why use it?
It gives contributors one set of rules for making changes safely and consistently across related repositories. The input does not provide broader coding capabilities beyond these project instructions.

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/benseverndev-oss/goldenmatch/cursorrules
Clone the repo
git clone --depth 1 https://github.com/benseverndev-oss/goldenmatch

Made for: Cursor.

Per session 1,317 This file is loaded in full into every session.
When invoked 1,317 The same file — it is already loaded in full.
Security scan B 1 finding. 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.01317 $0.01317
Opus 5 $0.00659 $0.00659
Sonnet 5 $0.00263 $0.00263
Haiku 4.5 $0.00132 $0.00132

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

Security

Grade B, and why

cursorrules scanned grade B with 1 finding 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- System Python for Postgres: `sudo rm -f /usr/lib/python3/dist-packages/typing_extensions.py` then `sudo pip install --break-system-packages goldenmatch`
packages/rust/extensions/.cursorrules · 74 lines

How it starts

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

GoldenMatch Extensions

Native SQL extensions for GoldenMatch (D:\show_case\goldenmatch).

  • Main repo: D:\show_case\goldenmatch -- Python entity resolution toolkit (v1.1.0+).
  • This repo: Rust bridge + Postgres extension + DuckDB Python UDFs
  • PyPI packages: goldenmatch (Python), goldenmatch-duckdb (DuckDB UDFs)

Branch & Merge SOP (all Golden Suite repos)

  • Feature work goes on feature/<name> branches, never directly to main
  • Merge via squash merge PR (watchers see PR activity, history stays clean)
  • PR title format: feat: <description> or fix: <description>
  • PR body: summary bullets + test plan
  • Merge when: tests pass, docs updated. Days not weeks.
  • After merge: delete remote branch

Environment

  • Windows 11, bash shell (Git Bash) -- use Unix paths
  • Two GitHub accounts: benzsevern (personal, for this repo) and benzsevern-mjh (work)
  • MUST gh auth switch --user benzsevern before push, switch back to benzsevern-mjh after
  • Rust 1.94.0 at C:\Users\bsevern\.cargo\bin -- must set RUSTUP_HOME="C:/Users/bsevern/.rustup" and CARGO_HOME="C:/Users/bsevern/.cargo" in every bash command
  • No admin privileges -- no LLVM/libclang, no WSL2. pgrx builds only work in CI (Linux)
  • PostgreSQL 16 portable at C:\Users\bsevern\tools\pg16portable\pgsql
  • Bridge crate compiles locally. Postgres crate requires Linux (CI only).

Architecture

  • Rust workspace (Cargo.toml) contains only bridge/ crate
  • postgres/ is excluded from workspace (exclude = ["postgres"]) -- pgrx 0.12.9 bug with SQL generation in workspace mode
  • duckdb/ is a standalone Python package (not Rust)

bridge/ (goldenmatch-bridge)

  • Shared crate: embeds CPython via pyo3, calls goldenmatch Python API
  • api.rs -- wrappers for dedupe, match, score_strings, score_pair, explain_pair, dedupe_pairs (structured), dedupe_clusters (structured)
  • convert.rs -- JSON <-> Polars DataFrame conversion (future: Arrow C Data Interface)
  • error.rs -- BridgeError enum with From impls for PyErr and ArrowError

Read the full file on GitHub · 74 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 · 74 lines · 1,317 tokens per session scan B 8ee84a9d5cb2

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository benseverndev-oss/goldenmatch (129 stars, last pushed 3d ago), licensed MIT. It adds 1,317 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.