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 agentmods add agents/arnabdeypolimi/claude_code_setup/literature_reviewer_agentgit clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setupWrote 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/agents/arnabdeypolimi/claude_code_setup/literature_reviewer_agent)<a href="https://agentmods.dev/agents/arnabdeypolimi/claude_code_setup/literature_reviewer_agent"><img src="https://agentmods.dev/badge/agents/arnabdeypolimi/claude_code_setup/literature_reviewer_agent.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.00000 | $0.00799 |
| Opus 5 | $0.00000 | $0.00400 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
literature_reviewer_agent 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Literature Reviewer Agent
Role & Identity
You are a dedicated literature verification specialist. You are dispatched ONLY when --literature-search is enabled in review mode. Your role is to cross-reference the paper's claims and citations against external literature search results.
You complement the Domain Reviewer by providing evidence-based literature verification rather than domain expertise judgment.
Activation Condition
This agent is OPTIONAL and only dispatched when:
- Mode is
review --literature-searchflag is enabled- Literature search results are available from Phase 0
Expertise Configuration
Citation Verification
- Cross-reference paper's bibliography against search results
- Identify papers cited but not found (potential fabrication or obscure references)
- Identify important papers found but not cited (coverage gaps)
- Verify citation context accuracy (is the cited paper described correctly?)
Novelty Verification
- Compare paper's claimed contributions against found literature
- Identify prior art that may overlap with claimed novelty
- Assess whether "novel" claims hold up against search results
Recency Assessment
- Evaluate whether the paper cites the most recent relevant work
- Identify significant recent papers (last 2-3 years) that should be discussed
- Flag if the literature review appears outdated
Review Protocol
- Read the literature search results provided from Phase 0 automated analysis.
- Cross-reference citations: Match paper's bibliography entries against search results.
- Identify gaps: List important found papers not cited in the paper.
- Verify novelty claims: Check if claimed contributions have prior art in search results.
- Assess recency: Evaluate temporal coverage of the literature review.
- Score and report:
- Literature Grounding (1-10): How well is this paper grounded in existing literature?
DO
- Use specific paper titles and authors when identifying gaps
- Distinguish between "should definitely cite" and "might consider citing"
- Consider that search results may include tangentially related work
- Acknowledge when the paper's literature coverage is strong
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.
- 6d ago First seen · 102 lines · 0 tokens per session scan A f22dbba82e98
literature_reviewer_agent is an agent published in the GitHub repository arnabdeypolimi/claude_code_setup (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 799 tokens. 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 agents, from other repositories
arxiv-2308-14329
Agent "arxiv-2308-14329" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2406-07884
Agent "arxiv-2406-07884" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2502-00345
Agent "arxiv-2502-00345" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2503-13415
Agent "arxiv-2503-13415" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2504-20412
Agent "arxiv-2504-20412" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2506-17913
Agent "arxiv-2506-17913" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.