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 runesleo/x-reader --skill link-readergit clone --depth 1 https://github.com/runesleo/x-readerWrote 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/runesleo/x-reader/link-reader)<a href="https://agentmods.dev/skills/runesleo/x-reader/link-reader"><img src="https://agentmods.dev/badge/skills/runesleo/x-reader/link-reader/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/runesleo/x-reader/link-reader"><img src="https://agentmods.dev/badge/skills/runesleo/x-reader/link-reader.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.00076 | $0.01577 |
| Opus 5.5 | $0.00030 | $0.00631 |
| Sonnet 5.5 | $0.00015 | $0.00315 |
| Haiku 4.5 | $0.00008 | $0.00158 |
Grade A, and why
link-reader 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Reader
Read the source first, then interpret it. Search snippets, preview cards, repost captions, and model paraphrases are not substitutes for the original.
This skill is the workflow layer on top of the repo’s x-reader skill (CLI/MCP fetch) and, when needed, the video skill (transcription). Install both when possible:
npx skills add runesleo/x-reader --skill x-reader --skill link-reader -g -y
Goal
- Explain the source — what it actually says, in plain language.
- Separate fact from opinion — author claims vs verifiable facts; verify key numbers when practical.
- Make it useful — only add project-specific or action advice when the user’s question or context makes it relevant. No filler sections.
Dropping a link is not a request to file a ticket, queue content, or run unrelated pipelines. Interpretation is the default outcome.
Default reading scope
When the user says “read this” / “what does this say” / sends a bare URL:
- Read the main post or article and material attachments (images, video, audio).
- For threads: parent context, continuations, quotes, and replies that change facts or conclusions — not only the top post.
- Follow outbound links that the post relies on (one hop; do not recurse endlessly).
- If comments or quotes are missing, empty, or blocked, say so with counts or platform limits — do not pretend full thread coverage from a high-vote sample.
Book lists / “digest this book”: read legally accessible chapters, author pages, and reliable reviews; output principles and limits of evidence, not a reading list alone. Do not claim full-book coverage without the text; do not bypass paywalls.
Tool routing (x-reader only)
Use one primary fetch path; reuse evidence you already fetched in the same turn.
| Need | Tool |
|---|---|
| Any supported URL | x-reader CLI: "$XR_BIN" "URL" --json (bootstrap from skills/x-reader/SKILL.md) |
| Batch URLs | "$XR_BIN" url1 url2 --json or MCP read_batch |
| Platform / readiness | "$XR_BIN" doctor or MCP detect_platform |
| Attached video/audio matters | After text/metadata fetch, use skills/video/SKILL.md (subtitles → Whisper) |
| Structured analysis after read | Optional skills/analyzer/SKILL.md |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 120 lines · 76 tokens per session scan A f29d5f02056c
link-reader is a skill published in the GitHub repository runesleo/x-reader (978 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,577 once invoked, about $0.0003 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-10-24.
Other skills, from other repositories
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…
mcp-tools-reference
MUST READ before first MCP tool call in a session. Complete Envoy tool catalog with parameters and usage.
td-api-reference
MUST READ before writing TD Python via executepython, setdatcontent, or editdatcontent, and before any heavy build. Parameters, storage, operators, referencing, threading, cook model, heavy-build safety caps.
brief
Compile a conversational request into an Embody task brief (briefs/.md): skills to load, discovered anchors, verifiable success criteria, and gates -- then execute the work from that contract. User-invoked via /brief.
externalize-operator
MUST READ before calling externalizeop or saveexternalization. Required workflow steps.
multi-instance
Workflow for running multiple TD instances with Envoy, switching between them, and understanding the instance registry.