clear-eyed-reading

clear-eyed-reading is a skill for Codex from JinPLu/clear-eyed-reading-skills. It costs 115 tokens per session (3,492 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; $skill-name invocation.

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 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,492 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.00115 $0.03492
Opus 5 $0.00057 $0.01746
Sonnet 5 $0.00023 $0.00698
Haiku 4.5 $0.00012 $0.00349

Measured 12d ago against content hash bd99f99549f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

Origin

This is a copy

86% identical to clear-eyed-deep-reading — 24 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 · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Shared Clear-Eyed Reading Core

Help a reader with no prior exposure understand the work and take back interpretive and evaluative control from the authors' terminology, branding, and narrative. Demystify by completing four judgments: reconstruct the ordinary mechanism; trace where capabilities or knowledge come from; identify the genuine increment over the closest prior work; and explain how the reported result came about, whether the conclusion is warranted, or what lets a system do what it shows. Let this independent reconstruction raise or lower the evaluation. Critique claims and evidence, never the authors.

Four judgments

Keep these four judgments, and do not substitute a summary, a limitation list, or a popularity report for any of them:

  1. Ordinary mechanism — after names and branding are removed, what enters, what happens, and what leaves.
  2. Capability sources — which data, prior models, assumptions, rules, labels, human choices, instruments, implementation, post-processing, scale, or evaluation choices supply the observed ability.
  3. Genuine increment — for every important candidate contribution, what is inherited, what technically changed relative to the closest primary precedent, and what the field would lose without that change.
  4. Result attribution — what actually carries the result or conclusion, and which rival explanations remain consequential.

Scale verification to risk and depth

Identify the work and the version the conclusion will rest on. Never fill gaps from an abstract, caption, search snippet, or guess; say what cannot be checked.

Scale how far to read and search by two factors: conclusion risk (how much the four judgments would change if this were wrong) and the active depth profile. High-risk conclusions—technical novelty, field significance, that the new method caused the result, reuse readiness, claim stability, or that a weakness is absent—need correspondingly stronger primary evidence. The depth profile sets the search budget; it does not change what the four judgments mean.

Read the full file on GitHub · 127 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. 12d 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 26d ago), licensed MIT. It adds 115 tokens to every session and 3,492 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to clear-eyed-deep-reading, differing in 24 lines, and is treated as a copy.

Related

Other skills, from other repositories

report-slides

Use when creating presentations and research reports, especially diagram-heavy decks with architecture, flowcharts, timelines, charts, conceptual illustrations, or editable PPTX output.

zi-yue-1129/research-lab-skills · 35 tokens

academic-paper

12-agent academic paper writing pipeline. 10 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE…

zi-yue-1129/research-lab-skills · 127 tokens

academic-pipeline

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification…

zi-yue-1129/research-lab-skills · 106 tokens

academic-paper-reviewer

Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on…

zi-yue-1129/research-lab-skills · 104 tokens

deep-research

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring…

zi-yue-1129/research-lab-skills · 225 tokens

research-log

Record, manage, and query research experiment logs. Use when the user wants to log an experiment result, amend an existing entry, view recent logs, rebuild the index, or plan, execute, repeat, or diagnose research in a project containing docs/researchlog/. Triggers on phrases like "log this experiment", "record…

zi-yue-1129/research-lab-skills · 135 tokens