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-syncgit 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-sync)<a href="https://agentmods.dev/skills/ahmedtawfeeq1/loredex/loredex-sync"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-sync/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-sync"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-sync.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.00058 | $0.00216 |
| Opus 5.5 | $0.00023 | $0.00086 |
| Sonnet 5.5 | $0.00012 | $0.00043 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
loredex-sync 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 1mo 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-sync
npx -y loredex@latest sync
Commits any local dex changes, pulls the remote with rebase, pushes. Safe to run any
time; offline it degrades to a local commit and says so. If it reports the dex isn't a
git repo, run npx -y loredex@latest init --sync git first and (for team sharing) add a
private remote: git -C <dex> remote add origin <url>.
handoff and handoffs already sync automatically — this command is for everything else
(e.g. after a big adopt or curate the team should see).
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.
- 1mo ago First seen · 19 lines · 58 tokens per session scan A a8750659df56
loredex-sync is a skill published in the GitHub repository ahmedtawfeeq1/loredex (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 216 once invoked, about $0.0002 per session on Opus 5.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
unforgit-memory
Use Unforgit MCP tools as durable repository memory for decisions, conventions, gotchas, and playbooks.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
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'.
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.