clear-eyed-reading

clear-eyed-reading is a skill for Codex from JinPLu/clear-eyed-reading-skills. It costs 131 tokens per session (3,278 once invoked), scanned A, a copy of clear-eyed-deep-reading, MIT.

A method for understanding research papers, technical articles, and similar writing by explaining how they work, what enables their results, and what they genuinely add.

In plain words
What is it for?
Use it to examine a paper or article, trace where its capabilities come from, compare its contribution with earlier work, and judge whether its claims are justified.
Why use it?
It helps readers separate the actual mechanism and evidence from specialized terminology, branding, or unsupported conclusions.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions subagents.

Good fit Use it to examine a paper or article, trace where its capabilities come from, compare its contribution with earlier work, and judge whether its claims are justified.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading
Install

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.

Any agent
npx skills add JinPLu/clear-eyed-reading-skills --skill clear-eyed-reading
Clone the repo
git clone --depth 1 https://github.com/JinPLu/clear-eyed-reading-skills

Made for: Codex.

Wrote 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.

agentmods badge for clear-eyed-reading

README.md
[![agentmods](https://agentmods.dev/badge/skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading/github.svg)](https://agentmods.dev/skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading)
Your own site
<a href="https://agentmods.dev/skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading"><img src="https://agentmods.dev/badge/skills/jinplu/clear-eyed-reading-skills/clear-eyed-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.

agentmods 80×15 button for clear-eyed-reading

Your own site · 80×15
<a href="https://agentmods.dev/skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading"><img src="https://agentmods.dev/badge/skills/jinplu/clear-eyed-reading-skills/clear-eyed-reading.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00131 $0.03278
Opus 5.5 $0.00052 $0.01311
Sonnet 5.5 $0.00026 $0.00656
Haiku 4.5 $0.00013 $0.00328

Measured 1mo ago against content hash 3a5e6cd80bf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

clear-eyed-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.

Origin

This is a copy

86% identical to clear-eyed-deep-reading — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/clear-eyed-reading/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 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.

  1. What does it actually do? Strip the names: what goes in, what happens at each step, what comes out.
  2. 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.
  3. 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.
  4. 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.

Read the full file on GitHub · 147 lines

Files

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.

Changes

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.

  1. 1mo ago Changed 3a5e6cd80bf4
  2. 1mo ago Changed · +20 lines · +16 tokens per session a28be55e8274
  3. 2mo ago First seen · 127 lines · 115 tokens per session scan A bd99f99549f3

Subscribe to this mod's changes

clear-eyed-reading is a skill published in the GitHub repository JinPLu/clear-eyed-reading-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 3,278 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to clear-eyed-deep-reading, differing in 27 lines, and is treated as a copy.

Related

clear-eyed-reading compared with skills from other repositories

clear-eyed-reading next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
clear-eyed-readingJinPLu/clear-eyed-reading-skillsSkill41mo agoMITA131Codex
report-slideszi-yue-1129/research-lab-skillsSkill9yesterdaynoneA35Claude Code
academic-pipelinezi-yue-1129/research-lab-skillsSkill9yesterdaynoneA106Claude Code
academic-paperzi-yue-1129/research-lab-skillsSkill9yesterdaynoneA131Claude Code
deep-researchzi-yue-1129/research-lab-skillsSkill9yesterdaynoneA225Claude Code
academic-paper-reviewerzi-yue-1129/research-lab-skillsSkill9yesterdaynoneA104Claude Code
research-logzi-yue-1129/research-lab-skillsSkill9yesterdaynoneA135Claude Code