setup-automation

A set of rules for running an automatic setup in Cursor, a code editor with agent features.

In plain words
What is it for?
Use it when the user explicitly asks Cursor to run setup through @setup-automation.mdc.
Why use it?
It defines when setup should run and prevents the setup instruction from being used at the wrong time.

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/shimayuz/note-com-mcp/setup-automation
Clone the repo
git clone --depth 1 https://github.com/shimayuz/note-com-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,613 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin unknown 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.00000 $0.01613
Opus 5 $0.00000 $0.00807
Sonnet 5 $0.00000 $0.00323
Haiku 4.5 $0.00000 $0.00161

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

Security

Grade D, and why

setup-automation scanned grade D with 2 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

2. `cat ~/.cursor/mcp.json` で設定ファイルのパスが正しいか確認

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf node_modules package-lock.json
.cursor/rules/setup-automation.mdc · 246 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 246 lines · 0 tokens per session scan D 0a567595e930

Subscribe to this mod's changes

setup-automation is a cursor rule published in the GitHub repository shimayuz/note-com-mcp (29 stars, last pushed 9d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,613 tokens. A static security scan graded it D with 2 findings (reads mcp configuration, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.