general-rule

Project-wide rules for how a coding assistant should analyze and edit code, including response language, formatting, uncertainty, links, and reporting changes. The excerpt is written in Japanese but asks the assistant to respond politely in Japanese.

In plain words
What is it for?
Use them to guide code analysis, edits, technical explanations, error reports, file references, and project-specific architecture rules.
Why use it?
They set shared expectations for assistant behavior across the project and tell it how to handle unknowns and unresolved questions.

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/showcase-gig-platform/cursor-rules-initializer/general-rule
Clone the repo
git clone --depth 1 https://github.com/showcase-gig-platform/cursor-rules-initializer

Made for: Cursor.

Per session 434 This file is loaded in full into every session.
When invoked 434 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.00434 $0.00434
Opus 5 $0.00217 $0.00217
Sonnet 5 $0.00087 $0.00087
Haiku 4.5 $0.00043 $0.00043

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

Security

Grade A, and why

general-rule 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.

.cursor/commands/cursor-rules-initializer/sample/rules/base/general-rule.mdc · 59 lines

What it actually says

generalルール

あなたは高度なコード解析・編集能力を備えたAIアシスタントです。以下のルールに従い作業を行ってください。


基本

  • 日本語で丁寧に回答してください
  • 技術用語は必要に応じて英語表記を併記可(例: Server Component、Server Action)
  • 不明点がある場合は推測に頼らないこと。ユーザーに確認を行う
  • 未解決の質問があれば、最後に列挙すること

強調とリンク

強調

  • 重要な用語やファイル名は太字**)で囲む
  • 禁止事項は「❌」、推奨事項は「✅」を併用可

リンク

  • ファイルパスはバッククォート(`)で囲む: `./src/domain/user/User.ts`
  • ディレクトリパスも同様: `src/domain/`
  • 外部URLは通常のMarkdownリンク: [リンクテキスト](URL)

回答の出力構造推奨パターン

変更作業の報告

### 実装内容
#### 変更ファイル
- `` `path/to/file.ts` ``: 変更内容の説明

#### 変更理由
- 理由1
- 理由2

エラー報告

### 問題
エラーの内容

### 原因
原因の説明

### 対応
対応方法の説明

技術スタック・レイヤーごとのルール

architecture.mdc を参照すること。

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 · 59 lines · 434 tokens per session scan A 48854ea6cd71

Subscribe to this mod's changes

general-rule is a cursor rule published in the GitHub repository showcase-gig-platform/cursor-rules-initializer (7 stars, last pushed 9mo ago), licensed MIT. It adds 434 tokens to every session, about $0.0022 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.