cursorrules

A project rule set that tells the coding agent to use Bun, a JavaScript runtime, and to follow specific planning, coding, documentation, and security practices.

In plain words
What is it for?
Use it to enforce Bun as the runtime, require a detailed plan before coding, and guide the agent toward complete, tested, readable code.
Why use it?
It gives the agent consistent instructions for how work should be planned and implemented in the project.

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/fradser/mcp-server-local-web-search/cursorrules
Clone the repo
git clone --depth 1 https://github.com/FradSer/mcp-server-local-web-search

Made for: Cursor.

Per session 151 This file is loaded in full into every session.
When invoked 151 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.00151 $0.00151
Opus 5 $0.00076 $0.00076
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

Measured 2d ago against content hash fe563459f615, 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 · 11 lines

What it actually says

This project use bun for runtime.

  • Follow the user's requirements exactly as provided.
  • Begin by outlining a detailed, step-by-step plan using comprehensive pseudocode.
  • Once the plan is confirmed, proceed to write the code.
  • Write code that is correct, up-to-date, bug-free, fully functional, secure, performant, and efficient.
  • Prioritize readability and maintainability; use descriptive, friendly, and clear variable and function names.
  • Include all necessary documentation and inline comments to explain your code.
  • Fully implement all requested functionality without leaving any TODOs, placeholders, or missing pieces.
  • Be concise and minimize any extraneous prose.
  • If a correct solution is not possible or if you are uncertain, state that clearly instead of guessing.
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 · 11 lines · 151 tokens per session scan A fe563459f615

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository FradSer/mcp-server-local-web-search (11 stars, last pushed 1y ago), licensed MIT. It adds 151 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-31.