cursorrules

A set of setup rules written in Japanese for requests such as “set up,” “configure,” “install,” or “make it usable.” It defines the procedure an agent should follow for those requests.

In plain words
What is it for?
Use it to guide setup, configuration, installation, and enablement requests made in the specified Japanese wording.
Why use it?
It gives the agent a consistent response path when a user asks to prepare or enable something.

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

Made for: Cursor.

Per session 1,344 This file is loaded in full into every session.
When invoked 1,344 The same file — it is already loaded in full.
Security scan C 1 finding. 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.01344 $0.01344
Opus 5 $0.00672 $0.00672
Sonnet 5 $0.00269 $0.00269
Haiku 4.5 $0.00134 $0.00134

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

Security

Grade C, and why

cursorrules scanned grade C with 1 finding 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.

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
.cursorrules · 234 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 · 234 lines · 1,344 tokens per session scan C d3ef2126ba14

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository shimayuz/note-com-mcp (29 stars, last pushed 8d ago), with no licence file. It adds 1,344 tokens to every session, about $0.0067 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.