paper-scrying

paper-scrying is a skill for Claude Code, Codex from Wondermonger-daydreaming/claude-skills-library. It costs 29 tokens per session (3,182 once invoked), scanned A, original, MIT.

A skeptical method for examining scientific papers by finding hidden assumptions, testing claims, spotting misleading reasoning, and proposing counter-experiments.

In plain words
What is it for?
Use it to stress-test research, challenge methods and statistics, detect possible scams, and design alternative tests.
Why use it?
It helps readers judge whether a paper's conclusions are supported and identify what could make them fail.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to stress-test research, challenge methods and statistics, detect possible scams, and design alternative tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wondermonger-daydreaming/claude-skills-library/paper-scrying
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 Wondermonger-daydreaming/claude-skills-library --skill paper-scrying
Clone the repo
git clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-library

Made for: Claude Code, 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 paper-scrying

README.md
[![agentmods](https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying/github.svg)](https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying)
Your own site
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying/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 paper-scrying

Your own site · 80×15
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-scrying.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,182 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 original No closer match found 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.00029 $0.03182
Opus 5 $0.00015 $0.01591
Sonnet 5 $0.00006 $0.00636
Haiku 4.5 $0.00003 $0.00318

Measured 8d ago against content hash 8b5334c22dcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

paper-scrying 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 8d 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.

skills/paper-scrying/SKILL.md · 268 lines

How it starts

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

PAPER-SCRYING ENGINE

A Skill for Skeptical Interrogation and Productive Heresy

OVERVIEW

This skill transforms reading into cross-examination. Where paper-hermeneutics seeks understanding and paper-riffing invites free association, paper-scrying approaches with productive suspicion—not cynicism, but rigorous skepticism. It asks: What must be true for this to work? What's hiding in the assumptions? What would break this? How might this be accidentally or deliberately misleading?

Core Principle: Every paper is a claim-structure vulnerable to interrogation. The authors made choices—of framing, methods, statistics, emphasis, omission. Scrying means making those choices visible, testing them against alternatives, and asking what the paper would prefer you not notice. Not to debunk, but to see clearly.

Etymological Note: Scrying—divination by gazing into reflective surfaces—here inverted. We gaze into the paper not to see futures but to see through surfaces, to catch the flicker of what's hidden beneath confident prose.


WHEN TO USE THIS SKILL

  • When asked to "stress-test" or "interrogate" a paper
  • When skepticism, criticism, or devil's advocacy is requested
  • When evaluating papers for replication potential or methodological soundness
  • When the paper's claims seem extraordinary and warrant extraordinary scrutiny
  • When preparing critical peer review or adversarial analysis
  • When teaching critical reading skills by demonstration
  • When the paper comes from fields prone to hype cycles or p-hacking

Do NOT use when:

  • User wants sympathetic understanding first (use hermeneutics, then scrying)
  • The paper is clearly reliable and criticism would be performative
  • Context suggests learning from the paper rather than attacking it
  • User explicitly wants positive/appreciative engagement
  • You haven't read carefully enough to criticize fairly

MODES OF SCRYING

MODE 1: THE ASSUMPTION EXCAVATION

Every paper rests on foundations it doesn't examine. Find them.

Read the full file on GitHub · 268 lines

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. 8d ago First seen · 268 lines · 29 tokens per session scan A 8b5334c22dcd

Subscribe to this mod's changes

paper-scrying is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 3,182 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

offensive-bug-identification

Systematic bug identification methodology: source code review patterns, black-box testing strategies, taint analysis, dangerous function hunting, data flow tracing, and automated scanning setup. Use for code audits, bug bounty triage, or building vulnerability identification pipelines.

SnailSploit/Claude-Red · 0 tokens

triage-issue

Verify an issue, persisted audit finding, or unresolved review finding against current code, classify it, and write only the contracted forge/ledger outcome. Supports independent batches and an immediate-fix review-finding route. Triggers: "triage-issue", "triage issue N", "triage this finding", "is this trigger met".

gtrabanco/agentic-workflow · 74 tokens

playwright-debugging

Diagnostic Playwright workflows for flaky or failing tests, including trace analysis, UI mode, and state isolation.

hzijad/playwright-agent-skills · 26 tokens

hyper-debug

Use when encountering a test failure, exception, regression, or unexpected behavior — before proposing fixes. Also when the user invokes /hyperclaude:hyper-debug. Forms hypotheses systematically instead of guess-and-check thrashing.

zeikar/hyperclaude · 46 tokens

qa-check

Auto-detects the project's tech stack, then audits for Accessibility, Performance, and Code Quality. Works across WordPress/PHP, Python, Node/JS, and static web projects.

stuartshields/claude-setup · 41 tokens

quantum-debugger

Debugs complex, hard-to-reproduce issues: race conditions, memory leaks, deadlocks, performance regressions, heisenbugs, and crash analysis. Uses scientific debugging methodology with hypothesis generation, systematic testing, and root cause isolation. Use this skill when the user reports intermittent crashes…

mturac/hermes-supercode-skills · 143 tokens