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/roccodaffuso/sift/sift-memorygit clone --depth 1 https://github.com/roccodaffuso/siftWhat 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.00043 | $0.00397 |
| Opus 5 | $0.00022 | $0.00198 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
sift-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.
What it actually says
Sift Memory
Use sift as local memory search for prior AI coding-assistant sessions.
Commands
Prefer the installed CLI:
sift index --json
sift "<query>" --limit 10 --json
sift "<query>" --tool codex --limit 10 --json
sift "<query>" --tool claude --limit 10 --json
sift "<query>" --tool cursor --limit 10 --json
sift "<query>" --tool opencode --limit 10 --json
sift show "<ref>" --json
sift list --limit 10 --json
When working inside the sift repo and the global command is unavailable, use:
node ./bin/sift.js index --json
node ./bin/sift.js "<query>" --limit 10 --json
node ./bin/sift.js show "<ref>" --json
node ./bin/sift.js list --limit 10 --json
Use sift index --full only when the user asks, parser/index behavior changed, or incremental results look stale.
Behavior
- Search before answering when local session history could materially improve accuracy.
- Use focused queries based on project names, command names, file names, bug symptoms, package names, or prior decisions.
- Follow only relevant search refs with
sift showwhen surrounding messages are needed. - Summarize only relevant findings. Do not paste large raw logs.
- Keep the workflow local: no network calls, no telemetry, no sync, no writes to Claude Code, Codex, Cursor, or OpenCode source logs/databases.
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 · 43 lines · 43 tokens per session scan A 2501f0c156c9
sift-memory is a cursor rule published in the GitHub repository roccodaffuso/sift (2 stars, last pushed 29d ago), licensed MIT. It adds 43 tokens to every session and 397 once invoked, about $0.0002 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…