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/lis186/taiwan-holiday-mcp/task-execution-documentationgit clone --depth 1 https://github.com/lis186/taiwan-holiday-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/lis186/taiwan-holiday-mcp/task-execution-documentation)<a href="https://agentmods.dev/rules/lis186/taiwan-holiday-mcp/task-execution-documentation"><img src="https://agentmods.dev/badge/rules/lis186/taiwan-holiday-mcp/task-execution-documentation.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00999 |
| Opus 5 | $0.00000 | $0.00500 |
| Sonnet 5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
task-execution-documentation 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- task-execution-documentation — 100% identical, 0 lines differ
What it actually says
任務執行後文件更新標準流程
核心原則
基於歷史執行模式，每次完成任務後必須按照以下順序更新相關文件：
標準執行流程
1. 任務完成後的必要文件更新
執行任務完成後，必須更新以下文件以反映實際狀況：
主要文件更新順序
- docs/dev-notes.md - 記錄重大決策、遇到的問題和解決方法
- docs/plan.md - 更新任務完成狀態和進度
- docs/verification/stage-1-verification.md - 更新驗證結果和測試狀態
2. dev-notes.md 更新內容標準
根據歷史模式，必須包含：
## Task X.X: [任務名稱] (完成日期)
### 重大技術決策
- 具體決策內容和理由
- 技術選型的考量因素
- 架構設計決定
### 遇到的問題及解決方案
- **問題現象**: 具體錯誤或問題描述
- **根本原因**: 深入分析問題成因
- **解決方案**: 具體解決步驟和代碼修改
- **學習心得**: 避免類似問題的經驗
### 品質指標達成情況
- 測試覆蓋率: X%
- 測試通過率: X/X
- 編譯狀態: 無錯誤/警告
- 其他品質指標
3. plan.md 更新標準
必須將完成的子任務標記為 ✅：
- [x] T1.1.1: 具體子任務描述 ✅
- [x] T1.1.2: 另一個子任務描述 ✅
4. verification 文件更新標準
根據歷史模式，必須包含：
## Task X.X: [任務名稱] ✅ (已完成於 YYYY-MM-DD)
### ✅ 實作完成項目
- 詳細的完成項目清單
- 技術實作細節
- 驗證結果
### 🔧 解決的問題
- 具體問題和解決方案記錄
### 📊 品質指標
- 測試結果統計
- 覆蓋率數據
- 效能指標
歷史執行模式分析
常見的更新要求格式
完成後進行驗證，最後把重要決策、發生的錯誤和解決方法寫入 @dev-notes.md驗證完成後把重大決定、遇到的問題和解決方式寫在 @dev-notes.md都完成後，驗證部分的文件 @stage-1-verification.md 和@plan.md 內的進度要反應最後的狀況
執行後的 Git 提交模式
- 總是在文件更新完成後執行
commit - 如果忘記更新某些文件，會要求
合併到前一次 commit - 使用
git commit --amend --no-edit進行合併
自動化檢查清單
在任務完成後，確認以下項目：
- dev-notes.md 已更新重大決策和問題解決方案
- plan.md 中的任務狀態已標記為完成 ✅
- verification 文件已反映最新的驗證結果
- 所有變更已提交到 Git
- 如有遺漏，已合併到前一次 commit
提示詞最佳化建議
當要求執行任務時，建議使用以下格式：
@prompt-optimizer.mdc 實作 Task X.X，完成後驗證，驗證完成後把重大決定、遇到的問題和解決方式寫在 @dev-notes.md，並更新 @plan.md 和 @stage-1-verification.md 的進度狀況
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.
- 4d ago First seen · 110 lines · 0 tokens per session scan A 26f559e926e1
task-execution-documentation is a cursor rule published in the GitHub repository lis186/taiwan-holiday-mcp (27 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 999 tokens. 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.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.