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.
npx agentmods add rules/zandereins/schliff/cursorrulesgit clone --depth 1 https://github.com/Zandereins/schliffWhat 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 | $0.00167 | $0.00167 |
| Opus 5 | $0.00084 | $0.00084 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00017 | $0.00017 |
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.
What it actually says
You are a senior TypeScript developer working on a Next.js 16 application.
Always use Server Components by default. Only add 'use client' when you need interactivity or browser APIs.
Use TypeScript strict mode. Never use any type — prefer unknown with type guards.
For data mutations, use Server Actions ('use server'), not Route Handlers. Route Handlers are for public APIs and webhooks only.
Use Tailwind CSS for styling. Follow the project's design tokens in tailwind.config.ts. Do not use inline styles or CSS modules.
Run npm run typecheck before committing. Fix all type errors — do not suppress with @ts-ignore.
Write tests for business logic. Use Vitest for unit tests, Playwright for E2E. Aim for 80% coverage on new code.
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.
- 2d ago First seen · 14 lines · 167 tokens per session scan A 457f467d2fac
cursorrules is a cursor rule published in the GitHub repository Zandereins/schliff (15 stars, last pushed 2d ago), licensed MIT. It adds 167 tokens to every session, about $0.0008 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-30.
Other cursor rules, from other repositories
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
scraper-models
Cursor rule "scraper-models" from TheWebScrapingClub/AI-Cursor-Scraping-Assistant, covering scraper types, e-commerce plp, e-commerce pdp, how to fill the scraper fields with values and how to create an e-commerce plp scraper.
scrapy
Cursor rule "scrapy" from TheWebScrapingClub/AI-Cursor-Scraping-Assistant, covering scrapy best practices, 1. code organization and structure, 1.1. directory structure, 1.2. file naming conventions and 1.3. module organization.
website-analysis
description: This rule provides a step by step guide to analyze a website and its code, in order to write a better Scrapy scraper. globs: /.py.
scrapy-step-by-step-process
description: This rule provides a step by step guide to follow for a successful Scrapy project. Read and implement the rules oncained in this file in first place. globs: /.py.