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 JinPLu/clear-eyed-reading-skills --skill clear-eyed-deep-readinggit clone --depth 1 https://github.com/JinPLu/clear-eyed-reading-skillsWrote 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/jinplu/clear-eyed-reading-skills/clear-eyed-deep-reading)<a href="https://agentmods.dev/skills/jinplu/clear-eyed-reading-skills/clear-eyed-deep-reading"><img src="https://agentmods.dev/badge/skills/jinplu/clear-eyed-reading-skills/clear-eyed-deep-reading/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/jinplu/clear-eyed-reading-skills/clear-eyed-deep-reading"><img src="https://agentmods.dev/badge/skills/jinplu/clear-eyed-reading-skills/clear-eyed-deep-reading.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.00145 | $0.03517 |
| Opus 5.5 | $0.00058 | $0.01407 |
| Sonnet 5.5 | $0.00029 | $0.00703 |
| Haiku 4.5 | $0.00015 | $0.00352 |
Grade A, and why
clear-eyed-deep-reading 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clear-eyed-reading — 86% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clear-Eyed Reading
Goal: a reader with no background finishes knowing what the work actually does, where its ability comes from, what is really new, and why its result came out the way it did — judged independently of the authors' names, branding, and framing. This can raise or lower the reader's opinion of the work; an undersold structural contribution deserves as much attention as an inflated claim. Critique claims and evidence, never the authors.
Four questions to answer
These drive the research. The writing section below says how to present the answers.
- What does it actually do? Strip the names: what goes in, what happens at each step, what comes out.
- Where does the ability come from? Which parts come from this work, and which from data, pretrained models, earlier methods, rules, labels, human choices, instruments, scale, tuning, post-processing, or the evaluation setup.
- What is really new? For every contribution the authors claim: what is borrowed, what changed compared with the closest earlier work, and what the field would lose without the change. Keep three things apart: how new the technique is, how much it matters, and how far the authors' claim exceeds or undersells the verified change.
- Why did the result come out this way? What actually carries the result or conclusion, and which other explanation — data, scale, baseline choice, metric, leakage, selection, tuning budget — could also produce it.
How to research
- Identify the exact work and version (preprint version, venue version). Read the primary text; never fill gaps from an abstract, caption, search snippet, or guess. Say plainly what you could not check. Do not bypass CAPTCHAs, logins, or other access controls; report the source as unchecked.
- List every contribution the authors claim — title, abstract, contribution list, named modules, method, figures, experiments, conclusion. Treat each as a claim to check, not as the outline of your explanation.
- For each claim, find the closest earlier work by more than one route: search, the work's references, later work citing it, older names for the same idea, neighboring fields. Compare against the earlier work's primary text, not its abstract. If the primary text is inaccessible, you may rely on a reliable secondary description such as a survey, but say so where the comparison is used. For supporting context that does not decide a judgment, an abstract is acceptable if you say so. Citation counts, downloads, and attention help find candidates; they never prove novelty or significance.
- Before accepting the authors' explanation of the result, ask what else could produce it.
- Look at decisive figures and tables yourself. Keep apart what you observed, what the authors say, external facts, your inference, and unknowns. Visual appeal is not evidence.
- Spend effort in proportion to risk: claims about novelty, significance, causation, reuse readiness, or the absence of a weakness need the strongest evidence. The depth profile sets the overall budget. Stop when more searching is unlikely to change the four answers, not at a fixed paper count.
- If independent subagents are available and allowed, you may split the checks — earlier work on the problem, earlier work on each component, other explanations of the result, material around the work — and reconcile afterwards. Otherwise do the same checks yourself in sequence.
- If outside research is impossible, answer from the work alone and say which judgments (novelty, field position, other explanations, material around the work) are unchecked. Do not score novelty or significance in that case.
What ships with it
1 file 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.
- 1mo ago Changed · +27 lines · +28 tokens per session 111f4ed20f19
- 2mo ago First seen · 131 lines · 117 tokens per session scan A 21ec04271b31
clear-eyed-deep-reading is a skill published in the GitHub repository JinPLu/clear-eyed-reading-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 3,517 once invoked, about $0.0006 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.
clear-eyed-deep-reading compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| clear-eyed-deep-readingJinPLu/clear-eyed-reading-skills | Skill | 4 | 1mo ago | MIT | A | 145 | Codex |
| report-slideszi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 35 | Claude Code |
| academic-pipelinezi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 106 | Claude Code |
| academic-paperzi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 131 | Claude Code |
| deep-researchzi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 225 | Claude Code |
| academic-paper-reviewerzi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 104 | Claude Code |
| research-logzi-yue-1129/research-lab-skills | Skill | 9 | yesterday | none | A | 135 | Claude Code |