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/preshan/GroceryListWrote 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/preshan/grocerylist/cursor-workflow-rules)<a href="https://agentmods.dev/rules/preshan/grocerylist/cursor-workflow-rules"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/cursor-workflow-rules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/preshan/grocerylist/cursor-workflow-rules"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/cursor-workflow-rules.svg" alt="Reviewed on agentmods" width="80" 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.00242 | $0.00242 |
| Opus 5.5 | $0.00097 | $0.00097 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
cursor-workflow-rules 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 1mo 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.
What it actually says
Cursor Workflow Rules
Work sequence
- Understand requirement and identify impacted files.
- Implement smallest correct change first.
- Verify with build/tests/lint for touched scope.
- Summarize what changed and what remains.
Editing guidelines
- Keep changes scoped to the requested task.
- Do not rewrite unrelated code.
- Preserve user-authored changes when present.
- Add brief comments only where logic is non-obvious.
Quality checks
- Run lint/checks after substantive edits.
- Prefer fixing root causes over suppressing warnings.
- Verify offline-critical flows when touching data or session logic.
Documentation discipline
- Update relevant docs in
docs/when scope/architecture/flow changes. - Keep implementation aligned with SRS and compliance documents.
Git hygiene
- Make atomic commits when asked to commit.
- Use clear commit messages focused on why.
- Avoid destructive git operations unless explicitly requested.
Product guardrail reminder
- Do not introduce cloud-only dependencies for core functionality.
- Maintain fast, accessible, and low-friction shopping flows.
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.
- 1mo ago First seen · 38 lines · 242 tokens per session scan A 14d5f62ee31f
cursor-workflow-rules is a cursor rule published in the GitHub repository preshan/GroceryList (2 stars, last pushed 5mo ago), licensed MIT. It adds 242 tokens to every session, about $0.0010 per session on Opus 5.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.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.