A project status template for tracking development phases, technology maturity, team availability, completed work, active tasks, testing, reviews, blockers, and expected completion.

Use it to record feature progress, infrastructure work, testing status, next actions, blockers, and delivery estimates.

It helps an agent or team see what is finished, what is being worked on, and what still needs attention. The supplied file is largely a blank template.

progress — Cursor rule by Hansonli05

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/hansonli05/cursor-rules-system/progress

Clone the repo

git clone --depth 1 https://github.com/Hansonli05/Cursor-rules-system

Made for: Cursor.

Per session 1,351 This file is loaded in full into every session.

When invoked 1,351 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5	$0.01351	$0.01351
Opus 5	$0.00675	$0.00675
Sonnet 5	$0.00270	$0.00270
Haiku 4.5	$0.00135	$0.00135

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

Security

Grade A, and why

progress 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/memory-bank/progress.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.

Progress

Project Status Overview

[GOAL] Current Phase: [Phase name and overall objective] [TECH] Technology Maturity: [How stable is the current tech stack] [TEAM] Team Status: [Team size, roles, availability]

[COMPLETE] Features & Components

Core Infrastructure

[COMPLETE] [Infrastructure Item 1] - [Brief description]
[COMPLETE] [Infrastructure Item 2] - [Brief description]

User Features

[COMPLETE] [Feature 1] - [Description, completion date]
[COMPLETE] [Feature 2] - [Description, completion date]

Technical Features

[COMPLETE] [Technical Feature 1] - [Description, completion date]
[COMPLETE] [Technical Feature 2] - [Description, completion date]

[IN_PROGRESS] Current Work

Active Development

[IN_PROGRESS] [Feature/Task 1] - [Current status, blocker if any]
- Progress: [Percentage or milestone]
- Next Steps: [Immediate next actions]
- ETA: [Expected completion]
[IN_PROGRESS] [Feature/Task 2] - [Current status, blocker if any]
- Progress: [Percentage or milestone]
- Next Steps: [Immediate next actions]
- ETA: [Expected completion]

Under Review

[TESTING] [Item 1] - [What's being tested or reviewed]
[TESTING] [Item 2] - [What's being tested or reviewed]

[PENDING] Planned Work

Next Sprint/Phase

[READY] [Planned Item 1] - [Description and priority]
[READY] [Planned Item 2] - [Description and priority]

Backlog (Prioritized)

[PRIORITY] [High Priority Item] - [Description and why it's important]
[Medium Priority Item] - [Description]
[Lower Priority Item] - [Description]

[BLOCKED] Blocked Items

[BLOCKED] [Blocked Item 1] - [Description]
- Blocker: [What's blocking this]
- Owner: [Who can unblock this]
- Impact: [What this affects]
[BLOCKED] [Blocked Item 2] - [Description]
- Blocker: [What's blocking this]
- Owner: [Who can unblock this]
- Impact: [What this affects]

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.

yesterday First seen · 143 lines · 1,351 tokens per session scan A 62daeddf94e5

Subscribe to this mod's changes

progress is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 1,351 tokens to every session, about $0.0068 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.

Memory and context Testing

progress