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/kleosr/cursorkleosrWrote 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/kleosr/cursorkleosr/workflow-memory)<a href="https://agentmods.dev/rules/kleosr/cursorkleosr/workflow-memory"><img src="https://agentmods.dev/badge/rules/kleosr/cursorkleosr/workflow-memory/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/kleosr/cursorkleosr/workflow-memory"><img src="https://agentmods.dev/badge/rules/kleosr/cursorkleosr/workflow-memory.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.00035 | $0.00035 |
| Opus 5.5 | $0.00014 | $0.00014 |
| Sonnet 5.5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
workflow-memory 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 Changed · -30 lines · -310 tokens per session 7884168f7e59
- 1mo ago First seen · 38 lines · 345 tokens per session scan A f7ca171f1d7a
workflow-memory is a cursor rule published in the GitHub repository kleosr/cursorkleosr (325 stars, last pushed 9d ago), with no licence file. It adds 35 tokens to every session, about $0.0001 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-30.
Other cursor rules, from other repositories
knowledge-management-rule
Comprehensive knowledge management system for capturing, organizing, and applying project knowledge.
100-memory-system
Comprehensive Memory System architecture for autonomous Cursor operation.
cursor-brain-os
Brain OS operating instructions — use MCP tools for project state, not source-code grep.
ai-context-management
Rule Name: ai-context-management Description: When the conversation context is getting long or the model is losing track of details, proactively summarize and restructure context.
avos-agent-workflow
Avos memory workflow for AI coding agents. Guides codebase search and history lookup.
00-workflow
Before responding to any request, call getsessioncontext.