Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/ahmedtawfeeq1/loredex-obsidian/loredex)<a href="https://agentmods.dev/rules/ahmedtawfeeq1/loredex-obsidian/loredex"><img src="https://agentmods.dev/badge/rules/ahmedtawfeeq1/loredex-obsidian/loredex/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/ahmedtawfeeq1/loredex-obsidian/loredex"><img src="https://agentmods.dev/badge/rules/ahmedtawfeeq1/loredex-obsidian/loredex.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.00234 | $0.00234 |
| Opus 5 | $0.00117 | $0.00117 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
loredex 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 9d 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.
This is a copy
100% identical to loredex — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Do not create standalone summary/report markdown files (SUMMARY.md, REPORT.md, NOTES.md, etc.) after finishing a task. If the work produced research, findings, analysis, or a plan worth keeping, write it with loredex frontmatter instead:
---
project: loredex-obsidian
topic: <kebab-case-topic>
type: research | finding | analysis | snapshot | note
date: YYYY-MM-DD
source: cursor
tags: []
---
Write it into this project's docs/ directory or the vault inbox at
/Users/tawfeeq/Loredex/_inbox. Run npx -y loredex@latest route to file it, or leave it for
the next loredex adopt.
Never add loredex: routed yourself — the router stamps it after filing.
A pre-stamped file is skipped as already-filed and will never reach the vault.
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.
- 9d ago First seen · 28 lines · 234 tokens per session scan A 084d30865309
loredex is a cursor rule published in the GitHub repository ahmedtawfeeq1/loredex-obsidian (0 stars, last pushed 1mo ago), licensed MIT. It adds 234 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to loredex, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
claude-obsidian
Portable rules for the claude-obsidian product and user vault workflows.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.