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/wiggitywhitney/mcp-commit-story/task_completion_workflowgit clone --depth 1 https://github.com/wiggitywhitney/mcp-commit-storyWhat 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.01159 | $0.01159 |
| Opus 5 | $0.00580 | $0.00580 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
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 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.
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
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.
- 2d ago First seen · 143 lines · 1,159 tokens per session scan A 5bbb8fc4ebe1
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.0058 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-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.
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.