task_completion_workflow

task_completion_workflow is a cursor rule for Cursor from wiggitywhitney/mcp-commit-story. It costs 1,159 tokens per session, scanned A, original, MIT.

A workspace rule for archiving completed task files while keeping their history. It moves finished tasks into a separate completed-tasks folder and updates references from active tasks.

In plain words
What is it for?
Verify that a task is complete, archive its task file, remove obsolete dependencies, and maintain an organized task workspace.
Why use it?
It keeps the active task list smaller without losing records of finished work or its dependencies.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Verify that a task is complete, archive its task file, remove obsolete dependencies, and maintain an organized task workspace.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/wiggitywhitney/mcp-commit-story/task_completion_workflow
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.

Clone the repo
git clone --depth 1 https://github.com/wiggitywhitney/mcp-commit-story

Made for: Cursor.

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

agentmods badge for task_completion_workflow

README.md
[![agentmods](https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow/github.svg)](https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow)
Your own site
<a href="https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for task_completion_workflow

Your own site · 80×15
<a href="https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/task_completion_workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,159 This file is loaded in full into every session.
When invoked 1,159 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01159 $0.01159
Opus 5.5 $0.00464 $0.00464
Sonnet 5.5 $0.00232 $0.00232
Haiku 4.5 $0.00116 $0.00116

Measured 1mo ago against content hash 5bbb8fc4ebe1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

task_completion_workflow 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 1mo 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/rules/task_completion_workflow.mdc · 143 lines

How it starts

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

Task Archival Process

Overview

When a task is completely finished, follow this archival process to maintain a clean, performant workspace while preserving all completed work.

Step 1: Verify Completion

[ ] All requirements in the task are met (check the Requirements checklist) [ ] All subtasks are marked complete [ ] Full test suite passes [ ] All deliverables are working as specified

Step 2: Archive Task File

[ ] Move task file from tasks/task_XXX.md to tasks/completed_tasks/task_XXX.md [ ] Preserve all task content and history in the archived file

Step 3: Clean Up Dependencies

[ ] Search all active task files in tasks/ directory for dependencies on the completed task [ ] Remove the completed task number from dependency lists of active tasks [ ] Update any task descriptions that reference the completed task if needed

Directory Structure

tasks/
├── task_001.md                  # Active task files
├── task_002.md
├── task_003.md
└── completed_tasks/
    ├── task_010.md             # Completed task files
    ├── task_015.md
    └── task_020.md

Benefits of Archival

  • Clean workspace: Only active tasks visible in main tasks/ directory
  • Preserved history: All completed work maintained in completed_tasks/
  • Dependency integrity: No broken references to completed tasks
  • Performance: Smaller active task set for better navigation

Validation

This process ensures:

  • Completed work is preserved with full context
  • Active task dependencies remain clean and accurate
  • No loss of historical information or decision context
  • Clean separation between active and completed work

This script will:

  • ✅ Automatically identify complete task units (main + all subtasks done)
  • ✅ Move task files to archive directory
  • ✅ Update completed_tasks.json with proper metadata
  • ✅ Remove archived tasks from main tasks.json
  • ✅ Report file size improvements and performance gains
  • ✅ Preserve work integrity by only archiving complete units

Read the full file on GitHub · 143 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. 1mo ago First seen · 143 lines · 1,159 tokens per session scan A 5bbb8fc4ebe1

Subscribe to this mod's changes

task_completion_workflow is a cursor rule published in the GitHub repository wiggitywhitney/mcp-commit-story (15 stars, last pushed 1y ago), licensed MIT. It adds 1,159 tokens to every session, about $0.0046 per session on Opus 5.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.