agentmods.dev

workflow-state

A set of workflow rules for handling large development initiatives called epics, which are broken into phases and smaller steps.

In plain words
What is it for?
It helps agents identify an epic from a natural-language request, record the current phase and step, and follow required project and architecture documents.
Why use it?
It keeps planning, architecture checks, and progress tracking in a consistent order instead of mixing them together.

Cursor rule for Cursor

33 1mo ago A scan 15 tokens original MIT
View the source file fbrbovic/cursor-rule-framework
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/fbrbovic/cursor-rule-framework/workflow-state
Clone the repo
git clone --depth 1 https://github.com/fbrbovic/cursor-rule-framework

Made for: Cursor.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,671 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.00015 $0.01671
Opus 5 $0.00008 $0.00835
Sonnet 5 $0.00003 $0.00334
Haiku 4.5 $0.00002 $0.00167

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

Security

Grade A, and why

workflow-state 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.

.cursor/rules/workflow-state.mdc · 183 lines

How it starts

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

workflow_state.md

Last updated: 2025-06-06

State

Phase: null Status: null
CurrentItem: null EpicReference: null EpicPhase: null EpicStep: null

Plan

Rules

Keep every major section under an explicit H2 (##) heading so the agent can locate them unambiguously.

[PHASE: ANALYZE]

  1. Read project_config.md, relevant code & docs.
  2. Epic Integration Logic:
    • If user request mentions epic work (e.g., "work on login from user management epic"), search epics.mdc
    • Identify matching epic, phase, and step from user's natural language description
    • Set CurrentItem to descriptive format, and set epic fields:
      • Set EpicReference = EPIC_NAME (if found)
      • Set EpicPhase = PHASE_NAME (if found)
      • Set EpicStep = STEP_NAME (if found)
    • If no epic context found, leave epic fields as null
  3. Summarize requirements. No code or planning.

[PHASE: BLUEPRINT]

  1. Architecture Validation: Read architecture.mdc to understand current architecture and validate planned changes align with existing patterns and decisions.
  2. If EpicReference exists, read epic context from epics.mdc for step requirements and acceptance criteria.
  3. Architecture Impact Assessment: Evaluate if planned work requires architectural changes or updates.
  4. Decompose task into ordered steps.
  5. Write pseudocode or file-level diff outline under ## Plan.
  6. Plan Architecture Updates: Include steps to update architecture.mdc if architectural changes are being made.
  7. Set Status = NEEDS_PLAN_APPROVAL and await user confirmation.

[PHASE: CONSTRUCT]

  1. Follow the approved ## Plan exactly.
  2. After each atomic change:
    • run test / linter commands specified in project_config.md
    • capture tool output in ## Log
  3. Architecture Updates: When implementing architectural changes, update architecture.mdc with new patterns, decisions, or modifications.
  4. On success of all steps, set Phase = VALIDATE.

Read the full file on GitHub · 183 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. 2d ago First seen · 183 lines · 15 tokens per session scan A e4dba623a596

Subscribe to this mod's changes

workflow-state is a cursor rule published in the GitHub repository fbrbovic/cursor-rule-framework (33 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,671 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-30.

PlanningProductivity
Related

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.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

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.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens