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.
npx agentmods add rules/firebolt-db/firebolt-memory-layer/fml-memorygit clone --depth 1 https://github.com/firebolt-db/firebolt-memory-layerWhat 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 | $0.01885 | $0.01885 |
| Opus 5 | $0.00942 | $0.00942 |
| Sonnet 5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
fml-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 yesterday.
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FML (Firebolt Memory Layer) - ALWAYS USE
You MUST use FML for persistent memory in EVERY conversation. This is not optional.
MANDATORY: Session Initialization (FIRST THING TO DO)
At the START of every conversation, BEFORE responding to any user request:
1. Call init_session with user_id "YOUR_USERNAME"
2. Call recall_memories with the user's query to get relevant context
3. Use the retrieved context to inform your response
During Every Conversation
Add to Working Memory
- After understanding the user's intent, add task context with
add_to_working_memory - Use content_type: "task_state" for current tasks
- Use content_type: "message" for important user statements
- Use content_type: "scratchpad" for your observations
🔄 AUTOMATIC Memory Extraction (DO THIS PROACTIVELY)
After EVERY response you give, silently scan for memorable content and store it WITHOUT being asked.
Auto-Store These Patterns (call store_memory automatically):
| Pattern Detected | Category | Importance |
|---|---|---|
| Bug fix or error resolution | procedural.workflow | 0.9 |
| User explains how something works | semantic.domain | 0.85 |
| Architecture/design decision made | episodic.decision | 0.9 |
| New tool/library/API usage learned | procedural.tool_usage | 0.85 |
| User preference expressed (likes/dislikes) | preference.style | 0.8 |
| Configuration or setup steps | procedural.workflow | 0.85 |
| Project-specific knowledge | semantic.project | 0.8 |
| Person/team mentioned with role | semantic.entity | 0.7 |
| Workaround or gotcha discovered | procedural.pattern | 0.9 |
| User corrects your mistake | semantic.domain | 0.85 |
How to Auto-Extract:
- Don't announce you're storing - just do it silently
- Summarize the learning (don't store raw conversation)
- Extract entities (tools, files, people, concepts)
- Set appropriate importance based on table above
- Include context that makes the memory useful later
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.
- yesterday First seen · 209 lines · 1,885 tokens per session scan A f19fe9fdfbf5
fml-memory is a cursor rule published in the GitHub repository firebolt-db/firebolt-memory-layer (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,885 tokens to every session, about $0.0094 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.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.