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/agentsystemlabs/nebula/nebula-memorygit clone --depth 1 https://github.com/AgentSystemLabs/nebulaWhat 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.00350 | $0.00350 |
| Opus 5 | $0.00175 | $0.00175 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade B, and why
nebula-memory scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
(`grep -ril '<symbol or TERM>' .claude/memory/entries` when the index is not enough). A recorded gotcha What it actually says
This repo keeps a shared MEMORY LOG in three layers: .claude/MEMORY.md is the index (one line per
task — date, title, the TERMS and files it is about — newest first), .claude/memory/gotchas.md holds
the standing gotchas (the traps that outlive their task, one line each, grouped by TERM), and
.claude/memory/entries/<date>-<slug>.md hold each task's full Asked / Did / Gotchas.
Before starting a task, read .claude/MEMORY.md and .claude/memory/gotchas.md in full, then open
the entry files whose index line names the TERMS, crate, symptom or file the user is asking about
(grep -ril '<symbol or TERM>' .claude/memory/entries when the index is not enough). A recorded gotcha
is a mine already stepped on; a recorded decision is settled unless the user reopens it. Entries
describe what was true when written, so confirm any file or flag they name still exists before relying
on it.
After finishing a task that changed code or behavior, diagnosed a bug, or turned up something
non-obvious, read .claude/skills/nebula-memory/SKILL.md and follow it: one entry file, one index line,
and any durable trap into the standing gotchas. Skip it for pure questions and trivial edits — the log
is only useful if it stays free of restated diffs. Run make memory-check afterwards.
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.
- 2d ago First seen · 22 lines · 350 tokens per session scan B 3fbba7580191
nebula-memory is a cursor rule published in the GitHub repository AgentSystemLabs/nebula (100 stars, last pushed yesterday), licensed MIT. It adds 350 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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
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.