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/genudo-ai/genudo_mcp/loredex)<a href="https://agentmods.dev/rules/genudo-ai/genudo_mcp/loredex"><img src="https://agentmods.dev/badge/rules/genudo-ai/genudo_mcp/loredex.svg" alt="Measured on agentmods" 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.00232 | $0.00232 |
| Opus 5 | $0.00116 | $0.00116 |
| Sonnet 5 | $0.00046 | $0.00046 |
| 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 7d 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: genudo_mcp
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.
- 7d ago First seen · 28 lines · 232 tokens per session scan A b3f8b99da838
loredex is a cursor rule published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 7d ago), licensed MIT. It adds 232 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
sofagent
A Cursor setup adapter that loads sofagent’s rules and knowledge at the start of a coding session, connects its MCP server, and runs change audits through Git hooks.
autonomous-development-workflow
When completing tasks autonomously without human supervision.
marie-kondo
Marie Kondo - organized minimalism, eliminates code that doesn't spark joy.
naming-stuff
When naming things - files, functions, urls, etc.
fixing-github-actions-builds
When the Github Actions build is broken.
pytest-what-to-test-and-mocking
We mock external API calls (mark live tests with @pytest.mark.flaky()). We reuse fixtures from conftest.py. We always use pytest as testing framework - never import unittest. We use pytest-mock (mocker fixture) and monkeypatch for mocking, not unittest.mock.