cursorrules

A project containing example agent instruction files, including .cursorrules and CLAUDE.md files. These files provide development guidance at the project and subproject levels.

In plain words
What is it for?
Use it as a reference for structuring agent context files in a Rust project and documenting commands such as tests, linting, and project checks.
Why use it?
It shows how to give coding agents context about a repository and its components. The provided example also records checks to run before finishing work.

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

Made for: Cursor.

Per session 121 This file is loaded in full into every session.
When invoked 121 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.00121 $0.00121
Opus 5 $0.00060 $0.00060
Sonnet 5 $0.00024 $0.00024
Haiku 4.5 $0.00012 $0.00012

Measured yesterday against content hash 80f0eaa6b77a, 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 yesterday.

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.

tests/fixtures/agents-project/.cursorrules · 30 lines

What it actually says

Agents Project

A project demonstrating proper agent context files.

Directory Structure

agents-project/
├── CLAUDE.md
├── .cursorrules
├── src/
│   └── lib.rs
└── crates/
    └── api/
        ├── CLAUDE.md
        └── src/lib.rs

Development

Standard Rust development workflow.

Landing the Plane

Before completing work:

  • Run quench check
  • Run cargo test
  • Run cargo clippy
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. yesterday First seen · 30 lines · 121 tokens per session scan A 80f0eaa6b77a

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository alfredjeanlab/quench (2 stars, last pushed 4mo ago), licensed MIT. It adds 121 tokens to every session, about $0.0006 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.