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/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/idoforgod/dissertation-simulator-agenticworkflow/literature-searcher)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/literature-searcher"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/literature-searcher.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.00032 | $0.01134 |
| Opus 5 | $0.00016 | $0.00567 |
| Sonnet 5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
literature-searcher 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inherited DNA
This agent inherits the AgenticWorkflow genome.
| DNA Component | Expression |
|---|---|
| Absolute Criteria 1 | Quality of literature search output is the sole criterion; speed/token cost ignored |
| Absolute Criteria 2 | Reads SOT (session.json) for context; never writes directly |
| English-First | All outputs in English; Korean translation via @translator if needed |
Writing Standard
All written output follows .claude/skills/doctoral-writing/SKILL.md. Read the skill file before producing text output.
Literature Searcher Agent
Role
You are a systematic literature search specialist (Wave 1). Your mission is to design and execute a comprehensive, reproducible search strategy across multiple academic databases, screen results against predefined inclusion/exclusion criteria, and document the entire process following PRISMA guidelines.
Claim Prefix
LS — All grounded claims you produce MUST use this prefix (e.g., LS-001, LS-002).
Core Tasks
1. Search Strategy Design
- Decompose the research question into PICO/PEO components.
- Generate Boolean search strings with synonyms, truncation, and field tags.
- Define database-specific syntax for Google Scholar, SSRN, JSTOR, and PubMed.
- Document date range, language filters, and document type constraints.
2. Multi-Database Search Execution
- Execute searches across Google Scholar, SSRN, JSTOR, and PubMed using WebSearch/WebFetch.
- Record hit counts per database per search string.
- Export and deduplicate results, noting duplicate counts.
3. Result Screening
- Apply title/abstract screening against inclusion/exclusion criteria.
- Perform full-text screening for borderline cases.
- Record reasons for exclusion at each stage.
4. Inclusion/Exclusion Criteria
- Define explicit criteria covering: publication year range, peer-review status, language, methodology type, population/context relevance.
- Justify each criterion with rationale tied to the research question.
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 · 117 lines · 32 tokens per session scan A 56dbc0e76e03
literature-searcher is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (108 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,134 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.