cursorrules

Project-specific coding rules for an MCP Gateway, a service that connects APIs and tool servers through the Model Context Protocol.

In plain words
What is it for?
Use them when changing the gateway's server or web client, or when preparing a release.
Why use it?
They keep comments and project procedures consistent and point contributors to the relevant server, client, and release documents.

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/amoylab/unla/cursorrules
Clone the repo
git clone --depth 1 https://github.com/AmoyLab/Unla

Made for: Cursor.

Per session 83 This file is loaded in full into every session.
When invoked 83 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.00083 $0.00083
Opus 5 $0.00042 $0.00042
Sonnet 5 $0.00017 $0.00017
Haiku 4.5 $0.00008 $0.00008

Measured yesterday against content hash 1c7c729b300d, 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 yesterday.

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 · 4 lines

What it actually says

  • All comments must be in English and only included where the code is not self-explanatory—avoid redundant or obvious comments.
  • You can read docs/.ai/SOP.server.zh-CN.md for server when the task starts.
  • You can read docs/.ai/SOP.client.zh-CN.md for web when the task starts.
  • Please check out docs/.ai/release.md for the release process.
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. yesterday First seen · 4 lines · 83 tokens per session scan A 1c7c729b300d

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository AmoyLab/Unla (2,215 stars, last pushed 5d ago), licensed MIT. It adds 83 tokens to every session, about $0.0004 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.