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 skills/camusgit/evoquant/research-surveynpx skills add CamusGIT/EvoQuant --skill research-surveygit clone --depth 1 https://github.com/CamusGIT/EvoQuantWrote 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/camusgit/evoquant/research-survey)<a href="https://agentmods.dev/skills/camusgit/evoquant/research-survey"><img src="https://agentmods.dev/badge/skills/camusgit/evoquant/research-survey.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 | $0.00125 | $0.02143 |
| Opus 5 | $0.00063 | $0.01071 |
| Sonnet 5 | $0.00025 | $0.00429 |
| Haiku 4.5 | $0.00013 | $0.00214 |
Grade A, and why
research-survey 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 4d 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.
This is a copy
94% identical to research-survey — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Survey
Generates high-quality, survey-grade literature reviews from papers collected by paper-navigator.
paper-navigator (collect 30-120 papers)
↓
Stage 1: Generate Outline (query-type adaptive structure)
↓
Stage 2: Draft Survey (outline + top-30 papers)
↓
Stage 3: Expand Sections (draft + all papers, section-by-section)
↓
Stage 4: Generate Section Summaries
↓
Stage 5: Refine Summary Sections (Abstract/Intro/Conclusion)
↓
Stage 6: Assemble + References
When to Use
- User asks for a "literature review", "survey", "field overview", or "systematic review"
- User has collected papers and wants them synthesized into a structured report
- User wants to understand the full landscape of a research field
When NOT to Use
- Finding papers → use
paper-navigatorfirst, then come here - Generating research ideas → use
research-ideation - Writing a Related Work section for a paper → use
paper-writing
Dependency: paper-navigator
This skill requires papers as input. If the user hasn't provided papers, first invoke paper-navigator (Workflow 1, target 30-120 papers) to collect them.
CRITICAL: All paper discovery MUST use the paper-navigator skill and its scripts (scholar_search, citation_traverse, arxiv_monitor, recommend, etc.). Using WebSearch, WebFetch, or any generic web search tool for finding papers is PROHIBITED. Generic web search cannot access Semantic Scholar, citation graphs, or academic recommendation systems. Only paper-navigator provides the academic search infrastructure needed for survey-quality literature collection.
Stage 1: Generate Outline
This is a two-phase process. Different fields have different survey conventions — a clinical systematic review looks nothing like a CS methods survey. First generate a domain-appropriate template, then create the detailed outline.
Phase 1A: Generate Domain-Specific Survey Template
Before outlining, identify the field and adapt the structure:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 211 lines · 125 tokens per session scan A edbb48337ada
research-survey is a skill published in the GitHub repository CamusGIT/EvoQuant (215 stars, last pushed 17d ago), licensed Apache-2.0. It adds 125 tokens to every session and 2,143 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to research-survey, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
error-recovery
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
agentic-workflow-designer
Conversational skill that interviews users to design new agentic workflows.
security-review
How to review PRs for security — credentials, injection, workflow permissions, supply chain, git operation safety.
shogun-screenshot
スクリーンショットの取得・加工を行う。ローカルスクショから最新画像を取得、 PlaywrightでWebページをキャプチャ、画像のトリミング・リサイズ、機微情報を黒塗りマスキング。 記事執筆、レポート作成、UI確認、画像加工時に起動。 「スクショ」「スクリーンショット」「画面キャプチャ」「最新のスクショ」「画像加工」「トリミング」「マスク」「写メ」「写メ撮った」「スクショ撮った」で起動。 Do NOT use for: 画像生成（shogun-imagegenを使え）。.