cursorrules

A set of project rules for a React and Vite app that lets users manage a JSON settings file through a web interface. It specifies the file location, preferred styling tools, package manager, and TypeScript conventions.

In plain words
What is it for?
Use it when building or maintaining this app, especially when editing its interface, styles, buttons, JSON configuration handling, or TypeScript code.
Why use it?
It keeps code changes consistent and avoids common project mistakes, such as using the wrong package manager, leaving button types implicit, or using untyped values.

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

Made for: Cursor.

Per session 100 This file is loaded in full into every session.
When invoked 100 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.00100 $0.00100
Opus 5 $0.00050 $0.00050
Sonnet 5 $0.00020 $0.00020
Haiku 4.5 $0.00010 $0.00010

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

What it actually says

this is a simple react and vite project that allows users to manage a JSON file on their computer with a nice UI.

the file path is " ~/Library/Application\ Support/Claude/claude_desktop_config.json"

styling is done with tailwindcss and daisyui whenever possible

never use "any" as a type

always add the type=button property to buttons

always use bun over npm for this project

JSX elements without children should be marked as self-closing

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 · 14 lines · 100 tokens per session scan A b3f673d5b46b

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository amxv/mcp-manager (292 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 100 tokens to every session, about $0.0005 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.