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 skills add ahmedtawfeeq1/loredex --skill loredex-initgit clone --depth 1 https://github.com/ahmedtawfeeq1/loredexWrote 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/skills/ahmedtawfeeq1/loredex/loredex-init)<a href="https://agentmods.dev/skills/ahmedtawfeeq1/loredex/loredex-init"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-init/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/skills/ahmedtawfeeq1/loredex/loredex-init"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-init.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.00065 | $0.00360 |
| Opus 5 | $0.00032 | $0.00180 |
| Sonnet 5 | $0.00013 | $0.00072 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
loredex-init 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 12d 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.
What it actually says
/loredex-init
- If the user hasn't said which editor code links should open in, run
npx -y loredex@latest doctorfirst — if it shows exactly one installed editor, use it without asking. Otherwise ask: vscode, cursor, windsurf, or system default. - Run:
Omitnpx -y loredex@latest init [--vault <path>] [--type research|agent-ops] [--sync git] --editor <choice>--vaultto use the default (~/Loredex) or an already-registered dex.--sync gitgit-inits the dex and auto-commits after every route/curate.--type agent-opscreates an agent-ops dex — a client fleet (Manager ▸ Client ▸ Pipeline/Agent ▸ Stage) instead of a research dex; scaffold the fleet afterwards with/loredex-agent-ops. Default staysresearch. - Report what got created: dex path, project registration, and the conventions written
to
AGENTS.md,CLAUDE.md, and.cursor/rules/loredex.mdc. - If the project already has research markdown sitting in it, suggest
/loredex-adoptnext.
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.
- 12d ago First seen · 24 lines · 65 tokens per session scan A f013d9b819ba
loredex-init is a skill published in the GitHub repository ahmedtawfeeq1/loredex (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 360 once invoked, about $0.0003 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 skills, from other repositories
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.
fkf-learn
Stage verified fkf findings as reviewable wiki or project diffs. Use after a durable decision, pattern, status change, dead end, or skill lesson.
unforgit-memory
Use Unforgit MCP tools as durable repository memory for decisions, conventions, gotchas, and playbooks.
cc-wiki
Distill the user's /.claude history into a Quartz knowledge base. Runs preprocess.py, dispatches parallel project-digest agents, then parallel cross-cutting synthesis agents (people / companies / projects / concepts / workflows / tools / playbooks), writes the spine, installs Quartz, and starts the dev server. Single…
kmd-ingest
The write protocol for a markdown knowledge base (Obsidian-compatible, the LLM-wiki pattern) — personal or shared. Use for EVERY write into the KB — distilling a new or scraped source, promoting a finished artifact/report/lesson into the KB, filing a durable learning, insight, or query answer, or correcting/updating…