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 Wondermonger-daydreaming/claude-skills-library --skill paper-scryinggit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/paper-scrying)<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.
<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>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.00029 | $0.03182 |
| Opus 5 | $0.00015 | $0.01591 |
| Sonnet 5 | $0.00006 | $0.00636 |
| Haiku 4.5 | $0.00003 | $0.00318 |
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.
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.
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.
- 8d ago First seen · 268 lines · 29 tokens per session scan A 8b5334c22dcd
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.
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.
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".
playwright-debugging
Diagnostic Playwright workflows for flaky or failing tests, including trace analysis, UI mode, and state isolation.
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.
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.
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…