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 llv22/AutoResearchWithEyes --skill research-litgit clone --depth 1 https://github.com/llv22/AutoResearchWithEyesWrote 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/llv22/autoresearchwitheyes/research-lit)<a href="https://agentmods.dev/skills/llv22/autoresearchwitheyes/research-lit"><img src="https://agentmods.dev/badge/skills/llv22/autoresearchwitheyes/research-lit.svg" alt="Measured on agentmods" 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.00048 | $0.01877 |
| Opus 5 | $0.00024 | $0.00938 |
| Sonnet 5 | $0.00010 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
research-lit 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 7d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Literature Review
Research topic: $ARGUMENTS
Step 0: Argument Resolution
Before starting the workflow, determine whether $ARGUMENTS is a file path or a plain text topic.
- Detect file path: Check if
$ARGUMENTS(after trimming quotes/whitespace) looks like a file path — i.e., ends with.md,.txt,.pdf, or contains/or\. - If it's a file path:
- Read the file using the
Readtool. - Extract the research topic, context, constraints, and any scope guidance from the file content.
- Use the file content as the RESOLVED_TOPIC for all subsequent steps.
- Preserve any inline overrides appended after the path (e.g.,
spec.md — sources: local): split on—and pass overrides through.
- Read the file using the
- If it's plain text: Use
$ARGUMENTSdirectly as the RESOLVED_TOPIC.
From this point forward, all references to
$ARGUMENTSin the workflow mean RESOLVED_TOPIC (the file content or the original text).
Constants
- PAPER_LIBRARY — Local directory containing user's paper collection (PDFs). Check these paths in order:
papers/in the current project directoryliterature/in the current project directory- Custom path specified by user in
CLAUDE.mdunder## Paper Library
- MAX_LOCAL_PAPERS = 20 — Maximum number of local PDFs to scan (read first 3 pages each). If more are found, prioritize by filename relevance to the topic.
💡 Overrides:
/research-lit "topic" — paper library: ~/my_papers/— custom local PDF path/research-lit "topic" — sources: local— only search local PDFs/research-lit "topic" — sources: web— only search the web (skip all local)/research-lit "topic" — sources: local, web— local PDFs + web search
Data Sources
This skill checks multiple sources in priority order. All are optional — if a source is not configured or not requested, skip it silently.
Source Selection
Parse $ARGUMENTS for a — sources: directive:
- If
— sources:is specified: Only search the listed sources (comma-separated). Valid values:local,web,all. - If not specified: Default to
all— search every available source in priority order.
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.
- 7d ago First seen · 150 lines · 48 tokens per session scan A f0169f54fa86
research-lit is a skill published in the GitHub repository llv22/AutoResearchWithEyes (5 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,877 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…