dinner_execution

A Japanese-language procedure for carrying out dinner preparation from shopping through cooking, cleanup, and review. It uses project files, shell commands, and helper actions to read budgets, update shopping records, and move between phases.

In plain words
What is it for?
Loading dinner-project settings, managing shopping within a budget, recording completion times, updating the shopping list, starting cooking, and progressing through the defined dinner-preparation phases.
Why use it?
It turns a multi-step household task into a repeatable sequence with recorded times, budget information, status updates, and explicit transitions.

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/miyatti777/cursor_agent_rules_sample/dinner_execution
Clone the repo
git clone --depth 1 https://github.com/miyatti777/cursor_agent_rules_sample

Made for: Cursor.

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,282 The whole file, excluding the scripts and references it only reads on demand.
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.00032 $0.04282
Opus 5 $0.00016 $0.02141
Sonnet 5 $0.00006 $0.00856
Haiku 4.5 $0.00003 $0.00428

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

Security

Grade A, and why

dinner_execution 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.

.cursor/rules/dinner_execution.mdc · 487 lines

How it starts

The opening of the file, as written. The whole thing — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.

夕食実行ルール - 買い物・調理・片付け・振り返りフェーズ

description: "夕食の準備の実行フェーズに関するルール(買い物・調理・片付け・振り返り)"

1. 夕食の買い物 - 買い物管理フェーズ


trigger: "夕食の買い物" steps: - name: "load_project_path" action: "execute_shell" command: "cat .dinner_project_path" variable: "dinner_dir" message: "プロジェクトパスを読み込んでいます..."

- name: "load_variables"
  action: "execute_shell"
  command: "grep shopping_budget {{dinner_dir}}/shopping_list.md | cut -d':' -f2 | tr -d ' 円'"
  variable: "shopping_budget"
  message: "予算情報を読み込んでいます..."

- name: "manage_shopping"
  action: "call shopping_manager"
  params:
    shopping_list_path: "{{dinner_dir}}/shopping_list.md"
    budget: "{{shopping_budget}}"
  message: "買い物リストの管理を開始します。予算内で必要な食材を揃えましょう。"

- name: "record_shopping_time"
  action: "execute_shell"
  command: "date +%H:%M"
  variable: "shopping_end_time"
  message: "買い物完了時刻: {{shopping_end_time}}"

- name: "update_shopping_status"
  action: "append_to_file"
  path: "{{dinner_dir}}/shopping_list.md"
  template: "shopping_status_template"
  message: "買い物ステータスを記録しました"

- name: "shopping_complete"
  action: "confirm"
  message: "買い物が完了しました。次は「夕食の調理」と話しかけて調理フェーズに進んでください。"

2. 夕食の調理 - 調理プロセスフェーズ


trigger: "夕食の調理" steps: - name: "load_project_path" action: "execute_shell" command: "cat .dinner_project_path" variable: "dinner_dir" message: "プロジェクトパスを読み込んでいます..."

- name: "load_cooking_method"
  action: "read_file"
  path: "{{dinner_dir}}/recipe.md"
  variable: "recipe_content"
  message: "レシピ情報を読み込んでいます..."

- name: "ingredient_preparation"
  action: "call"
  target: "cooking_preparation"
  params:
    recipe_path: "{{dinner_dir}}/recipe.md"
    tasks_path: "{{dinner_dir}}/tasks.md"
  message: "材料の下準備を開始します。"

- name: "setup_cooking_timer"
  action: "execute_shell"
  command: "date +%s"
  variable: "cooking_start_timestamp"
  message: "調理開始時間を記録しています..."

Read the full file on GitHub · 487 lines

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 · 487 lines · 32 tokens per session scan A d89ffd44523a

Subscribe to this mod's changes

dinner_execution is a cursor rule published in the GitHub repository miyatti777/cursor_agent_rules_sample (3 stars, last pushed 1y ago), licensed MIT. It adds 32 tokens to every session and 4,282 once invoked, about $0.0002 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.