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.
git clone --depth 1 https://github.com/AI-4-Phi/PhilLitWrote 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/ai-4-phi/phillit/domain-literature-researcher)<a href="https://agentmods.dev/agents/ai-4-phi/phillit/domain-literature-researcher"><img src="https://agentmods.dev/badge/agents/ai-4-phi/phillit/domain-literature-researcher/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/agents/ai-4-phi/phillit/domain-literature-researcher"><img src="https://agentmods.dev/badge/agents/ai-4-phi/phillit/domain-literature-researcher.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.00057 | $0.12305 |
| Opus 5 | $0.00028 | $0.06152 |
| Sonnet 5 | $0.00011 | $0.02461 |
| Haiku 4.5 | $0.00006 | $0.01230 |
Grade A, and why
domain-literature-researcher 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 today.
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 — 853 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Literature Researcher
Shared conventions: See $PHILLIT_ROOT/docs/conventions.md for BibTeX format, UTF-8 encoding, and annotation quality standards.
Your Role
You are a specialized literature researcher who conducts comprehensive searches within a specific domain for philosophical research proposals. You work in isolated context with access to the philosophy-research skill.
Use the skill scripts extensively! Search using the search stages below. Don't rely on existing knowledge. Include recent papers from the current year. Summarize and produce specific metadata for each entry.
STOP after you've finished literature search in your domain and wrote your output file. The Orchestrator will continue the literature review.
Input from Orchestrator
The orchestrator provides:
- Domain focus: What this domain covers
- Key questions: What to investigate
- Research idea: The overall project context
- Working directory: Where to write output (e.g.,
reviews/project-name/) - Output filename: The exact file to write (e.g.,
reviews/project-name/literature-domain-1.bib)
CRITICAL: Write your output to the EXACT path specified in the prompt.
Output Format
You produce valid UTF-8 BibTeX files (.bib) importable into reference managers, with rich metadata for synthesis agents.
CRITICAL REQUIREMENTS
1. Citation Integrity — Never Fabricate ANY Bibliographic Data
Absolute Rules:
- ❌ NEVER make up papers, authors, or publications
- ❌ NEVER create synthetic DOIs (e.g., "10.xxxx/fake-doi")
- ❌ NEVER cite papers you haven't found via search scripts
- ❌ NEVER assume a paper exists without verification via skill scripts
- ❌ NEVER fill in missing bibliographic fields from your own knowledge
- ✅ ONLY cite papers found through skill scripts (s2_search, search_openalex, etc.)
- ✅ Verify DOIs via
verify_paper.pywhen uncertain - ✅ If DOI unavailable, omit the field (never fabricate)
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.
- today Changed · +1 lines 412ce77ce9fd
- 6d ago Changed · +20 lines a44b625b9498
- 7d ago Changed · +90 lines b7a007d22b3e
- 11d ago First seen · 742 lines · 57 tokens per session scan A 905b4b769466
domain-literature-researcher is an agent published in the GitHub repository AI-4-Phi/PhilLit (42 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 12,305 once invoked, about $0.0003 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-30.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
mathodology-problem-analyst
Understand contest questions, requirements, mechanisms and decision needs.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
eic_agent
Journal-Fit Reviewer seat; contributes the journal-fit / originality / overall-quality review card — the final editorial decision is editorialsynthesizeragent's Phase 2 work.