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-handoffsgit 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-handoffs)<a href="https://agentmods.dev/skills/ahmedtawfeeq1/loredex/loredex-handoffs"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-handoffs/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-handoffs"><img src="https://agentmods.dev/badge/skills/ahmedtawfeeq1/loredex/loredex-handoffs.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.00087 | $0.00403 |
| Opus 5 | $0.00044 | $0.00201 |
| Sonnet 5 | $0.00017 | $0.00081 |
| Haiku 4.5 | $0.00009 | $0.00040 |
Grade A, and why
loredex-handoffs 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-handoffs
In Claude Code, open handoffs are already injected into your context automatically at
session start (the plugin's SessionStart hook runs this check for you) — if you saw a
[loredex] N open handoff(s) block when the session began, act on it: read each brief
before planning related work, and consume after acting. Use this skill explicitly when
mid-session ("did anything new arrive?"), on an agent without the plugin, or when the user
asks directly.
To check on demand:
npx -y loredex@latest handoffs
This pulls the dex remote first, so teammates' fresh handoffs appear. For each open handoff listed:
- Read it (the path is printed) — it contains the objective, a brief written for this team, and a reading order of the source team's notes. Follow the reading order before planning any work that builds on it; this is the full context the interface artifact (Postman collection, API spec) alone doesn't carry.
- Plan/do the work with that context loaded.
- Mark it consumed once acted on:
Don't consume handoffs you only skimmed — open means "still owed attention."npx -y loredex@latest handoffs --consume <handoff-note-name>
Nothing listed? Say so and move on — don't invent pending work.
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 · 36 lines · 87 tokens per session scan A 6dd0b480f898
loredex-handoffs is a skill published in the GitHub repository ahmedtawfeeq1/loredex (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 403 once invoked, about $0.0004 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
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
capture-task
Capture a new task — create a draft or pending Task record from a rough idea or detailed spec. Use when asked to "add a task", "log a bug", "create a task", or "add to backlog".
refine-backlog
Refine the backlog — screen drafts, remove duplicates, fill in missing details, classify, link, and move to pending.
implement-task
Pick up and work on a binder Task — investigate bugs, discuss open questions, design solutions, write tests, or implement code. Use when asked to "work on", "pick up", "implement", or "fix" a task.
daily-brief
Narrate FKF's deterministic daily control surface. Use when an owner asks to prepare the day, get a daily brief, or identify today's priorities and collection gaps.