progress-state-agent

A workflow state manager for orchestrated coding runs. It keeps the active phase, wave, agents, resume point, blockers, and build, lint, and test status in WORKFLOWSTATE.md.

In plain words
What is it for?
Use it at the start of orchestration runs to resume work, track waves and agents, record blockers, and confirm state against the TODO list.
Why use it?
It gives later runs a reliable place to see where work stopped and what still blocks progress. It reduces confusion caused by duplicated or outdated task lists.

Agent 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 agents/kayaerhan/cursor-agent-tr/progress-state-agent
Clone the repo
git clone --depth 1 https://github.com/KayaErhan/cursor-agent-tr

Made for: Cursor.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 164 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.00029 $0.00164
Opus 5 $0.00015 $0.00082
Sonnet 5 $0.00006 $0.00033
Haiku 4.5 $0.00003 $0.00016

Measured 3d ago against content hash 2273d050de75, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

progress-state-agent 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 3d 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/agents/progress-state-agent.md · 16 lines

What it actually says

State yoneticisi. docs/WORKFLOW_STATE.md (schema v2) tek yazim noktasi — docs/AGENT_CONTRACTS.md.

Gorevler:

  • Aktif faz, dalga, aktif agent listesi
  • Resume noktasi, son basarili dogrulama
  • Blocker, retry, build/lint/test bayraklari
  • TODO ile state tutarliligi (TODO kopyasi state'e yazilmaz)

Her /proje_orkestra, /proje_workflow, /proje_devam basinda resume analizi.

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. 3d ago First seen · 16 lines · 29 tokens per session scan A 2273d050de75

Subscribe to this mod's changes

progress-state-agent is an agent published in the GitHub repository KayaErhan/cursor-agent-tr (6 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 164 once invoked, about $0.0001 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.