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.
npx agentmods add rules/miyatti777/cursor_agent_rules_sample/dinnergit clone --depth 1 https://github.com/miyatti777/cursor_agent_rules_sampleWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00040 | $0.03708 |
| Opus 5 | $0.00020 | $0.01854 |
| Sonnet 5 | $0.00008 | $0.00742 |
| Haiku 4.5 | $0.00004 | $0.00371 |
Grade A, and why
dinner 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.
This is a copy
100% identical to code-commenting-standards — 406 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
# 1. 夕食の準備 - 計画立案フェーズ
trigger: "夕食の準備"
steps:
- name: "start_info_collection"
action: "call"
target: "dinner_questions"
message: "夕食の準備をするにあたって、質問させてください"
- name: "confirm_dinner_start"
action: "confirm"
message: "以下の内容で夕食準備プロジェクトを開始します：{{info_collection}}"
- name: "get_current_date"
action: "execute_shell"
command: "date +%Y-%m-%d"
variable: "current_date"
message: "現在の日付を取得しています..."
- name: "create_dinner_dir"
action: "execute_shell"
command: "mkdir -p Dinner/{{current_date}}_{{dinner_menu}}"
variable: "dinner_dir"
message: "夕食準備用ディレクトリを作成しています..."
- name: "save_dinner_dir"
action: "execute_shell"
command: "echo {{dinner_dir}} > .dinner_project_path"
message: "プロジェクトパスを保存しています..."
- name: "create_dinner_plan"
action: "create_file"
path: "{{dinner_dir}}/plan.md"
template: "dinner_plan_template"
message: "夕食準備計画ファイルを作成しました"
- name: "create_recipe"
action: "create_file"
path: "{{dinner_dir}}/recipe.md"
template: "recipe_template"
message: "レシピファイルを作成しました"
- name: "create_tasks"
action: "create_file"
path: "{{dinner_dir}}/tasks.md"
template: "tasks_template"
message: "タスクリストを作成しました"
- name: "create_shopping_list"
action: "create_file"
path: "{{dinner_dir}}/shopping_list.md"
template: "shopping_list_template"
message: "買い物リストを作成しました"
- name: "plan_created"
action: "confirm"
message: "初期プランを作成しました。計画の詳細をご確認いただけますか？"
variable: "review_plan"
- name: "dinner_plan_next_steps"
action: "notify"
message: "これから夕食の準備を進めるには以下のステップがあります：\n\n1. 「夕食の計画改善」と言って計画を改善する\n2. 「夕食の買い物」と言って買い物フェーズに進む\n\n準備ができたら次に進んでください。"
# 1.5 夕食の計画改善 - 計画改善フェーズ
---
trigger: "夕食の計画改善"
steps:
- name: "load_project_path"
action: "execute_shell"
command: "cat .dinner_project_path"
variable: "dinner_dir"
message: "プロジェクトパスを読み込んでいます..."
- name: "load_dinner_menu"
action: "execute_shell"
command: "grep 'メニュー:' {{dinner_dir}}/recipe.md | head -1 | cut -d':' -f2 | tr -d ' '"
variable: "dinner_menu"
message: "メニュー情報を読み込んでいます..."
- name: "confirm_plan_improvement"
action: "confirm"
message: "「{{dinner_menu}}」の計画を改善します。どのような点を改善したいですか？"
variable: "improvement_needed"
- name: "start_feedback_collection"
action: "confirm"
message: "フィードバック収集を開始します。各質問に具体的に回答してください。準備はよろしいですか？"
variable: "start_feedback"
- name: "collect_plan_feedback"
action: "call"
target: "plan_feedback_questions"
params:
dinner_menu: "{{dinner_menu}}"
dinner_dir: "{{dinner_dir}}"
variable: "plan_feedback"
message: "プランについてのフィードバックを収集します..."
condition: "{{start_feedback}} == true"
- name: "create_feedback_summary"
action: "create_file"
path: "{{dinner_dir}}/feedback.md"
template: "feedback_summary_template"
message: "フィードバック概要ファイルを作成しました"
condition: "{{start_feedback}} == true"
- name: "update_plan_based_on_feedback"
action: "confirm"
message: "フィードバックを元にプランを更新しますか？\n\n収集したフィードバック：\n{{plan_feedback}}"
variable: "update_plan"
condition: "{{start_feedback}} == true"
- name: "update_recipe"
action: "modify_file"
path: "{{dinner_dir}}/recipe.md"
variable: "updated_recipe"
message: "レシピを更新しています..."
condition: "{{update_plan}} == true"
- name: "update_tasks"
action: "modify_file"
path: "{{dinner_dir}}/tasks.md"
variable: "updated_tasks"
message: "タスクリストを更新しています..."
condition: "{{update_plan}} == true"
- name: "update_shopping_list"
action: "modify_file"
path: "{{dinner_dir}}/shopping_list.md"
variable: "updated_shopping_list"
message: "買い物リストを更新しています..."
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.
- yesterday First seen · 406 lines · 40 tokens per session scan A d4b0d770eb93
dinner is a cursor rule published in the GitHub repository miyatti777/cursor_agent_rules_sample (3 stars, last pushed 1y ago), licensed MIT. It adds 40 tokens to every session and 3,708 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-commenting-standards, differing in 406 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.