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.
git clone --depth 1 https://github.com/synaptiai/prompt-decoratorsWrote 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.
[](https://agentmods.dev/rules/synaptiai/prompt-decorators/801-workflow-agile)<a href="https://agentmods.dev/rules/synaptiai/prompt-decorators/801-workflow-agile"><img src="https://agentmods.dev/badge/rules/synaptiai/prompt-decorators/801-workflow-agile.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00806 | $0.00806 |
| Opus 5 | $0.00403 | $0.00403 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
801-workflow-agile 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Workflow and core memory proceedure RULES that MUST be followed EXACTLY!
Critical Rule: First Ensure a .ai/prd.md file exists, if not, work with the user to create one so you know in full detail what the project is about. Critical Rule: This workflow rule is critical to your memory systems, all retention of what is planned or what has been completed or changed will be recorded in the .ai folder. it is critical that this information be retained in top quality and kept up to date. When you are unsure, reference the PRD, ARCH, current and previous stories as needed to guide you. If still unsure, dont ever guess - ask the user for help.
- When coming online, you will first check if a .ai/prd.md file exists, if not, work with the user to create one to you know what the project is about.
- If the PRD is not status: approved, you will ONLY have the goal of helping Improve the .ai/prd.md file as needed and getting it approved by the userto ensure it is the best possible document include the following:
- Very Detailed Purpose, problems solved, and task sequence.
- Very Detailed Architecture patterns and key technical decisions, mermaid diagrams to help visualize the architecture.
- Very Detailed Technologies, setup, and constraints.
- Unknowns, assumptions, and risks.
- It must be formatted and include at least everything outlined in the .cursor/templates/template-prd.md
- Once the .ai/prd.md file is created and the status is approved, Generate the architecture document .ai/arch.md draft - which also needs to be approved.
- The template for this must be used and include all sections from the template at a minimum: .cursor/templates/template-arch.md
- Once the .ai/arch.md is approved, create the draft of the first story in the .ai folder.
- Always use the .cursor/templates/template-story.md file as a template for the story. The story will be named .story.md added to the .ai folder
- Example: .ai/story-1.story.md or .ai/task-1.story.md
- You will wait for approval of the story before proceeding to do any work on the story.
- You are a TDD Master, so you will run tests and ensure tests pass before going to the next subtask or story.
- You will update the story file as subtasks are completed.
- Once a Story is complete, you will generate a draft of the next story and wait on approval before proceeding.
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.
- 8d ago First seen · 45 lines · 806 tokens per session scan A 47f751ec424e
801-workflow-agile is a cursor rule published in the GitHub repository synaptiai/prompt-decorators (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 806 tokens to every session, about $0.0040 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
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
task-tracking-basic
Basic task tracking for Level 2 Simple Enhancement tasks.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.