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-ideationnpx skills add CamusGIT/EvoQuant --skill research-ideationgit 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-ideation)<a href="https://agentmods.dev/skills/camusgit/evoquant/research-ideation"><img src="https://agentmods.dev/badge/skills/camusgit/evoquant/research-ideation.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.00151 | $0.04723 |
| Opus 5 | $0.00076 | $0.02361 |
| Sonnet 5 | $0.00030 | $0.00945 |
| Haiku 4.5 | $0.00015 | $0.00472 |
Grade A, and why
research-ideation 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 3d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Ideation
From research goal to ranked ideas and a detailed proposal.
Step 0: Load evo-memory (M_I)
↓
Step 1: Define Scope & Goal
↓
Step 2: Literature Grounding (MUST use local-paper-navigator scripts)
↓
Step 3: Generate Ideas (3 Anchor Papers × Innovator persona)
↓
Step 4: Refine Ideas (3 tracks × N iterations)
↓
Step 5: ELO Tournament → Present Top-3 to User
↓
Step 6: Update evo-memory (IDE)
↓
User Selects
↓
Step 7: Expand into Proposal
↓
Step 8: Validate and Iterate
When to Use
- User wants to find a research direction or brainstorm research ideas within a specific quant scope stage
- User wants to evaluate whether an idea is novel or worth pursuing
- User wants to rank or compare multiple research ideas
- User wants to generate a research proposal from an idea anchored to an existing paper
Note: This pipeline is optimized for quantitative research where incremental, anchor-first contributions are preferred over architectural redesigns.
When NOT to Use
- Finding/reading papers → use
local-paper-navigator - Literature survey report → use
research-survey - Planning a paper (story design, experiment plan) → use
paper-planning
Step 0: Load Prior Knowledge from evo-memory
Before any ideation begins, load Ideation Memory (M_I) from prior research cycles:
- Read M_I at
/memory/ideation-memory.md(refer toevo-memoryskill) - Select the top-2 entries (k_I=2) most relevant to the user's current goal by comparing each entry's Summary and Retrieval Tags against the goal
- Feasible directions from prior cycles → use as seeds in Step 3 (incorporate as candidate anchor directions alongside new ones, within the same scope stage)
- Unsuccessful directions marked as fundamental failures → use during idea pruning in Step 4 (prune any idea that matches a fundamental failure pattern)
- If M_I doesn't exist yet (first cycle), skip this step
This step prevents repeating known dead ends and builds on prior successes across research cycles.
What ships with it
13 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.
- assets/direction-summary-template.md 2.1 KB
- assets/idea-candidate-template.md 1.8 KB
- assets/paper-summary-template.md 895 B
- assets/proposal-template.md 5.8 KB
- assets/ranking-scorecard-template.md 1.1 KB
- references/baseline-feasibility.md 2.6 KB
- references/elo-ranking-guide.md 10 KB
- references/literature-tree.md 5.1 KB
- references/paper-reading.md 4.4 KB
- references/problem-selection.md 6.1 KB
- references/proposal-extension.md 12 KB
- references/solution-design.md 7.2 KB
- references/tree-search-protocol.md 7.7 KB
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.
- 3d ago First seen · 410 lines · 151 tokens per session scan A 27f2bed8dc11
research-ideation is a skill published in the GitHub repository CamusGIT/EvoQuant (215 stars, last pushed 17d ago), licensed Apache-2.0. It adds 151 tokens to every session and 4,723 once invoked, about $0.0008 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 skills, from other repositories
question-framing
Fill a slot-based question-framing schema (PICO, PECO, or SPIDER) from a paper's stated research question. Use this whenever the user wants a paper's research question structured into one of these standard clinical/qualitative-research question frames; this frames what question is being asked, it does not read or…
reforms-grading
Tactic: Grade an ML/CS paper's reproducibility configuration reporting as complete, partial, or none after checking that clinical appraisal tools do not apply. Use when the question is whether the work can be rerun.
labrat-operator
Use when operating a labrat lab with Codex: checking health, choosing the next phase prompt, supervising runtime cycles, auditing candidates, synthesizing recent evaluations, or writing checkpoint notes.
research-innovation-explorer
Build literature-grounded research-question candidate landscapes by collecting papers, generating A+B matrices, and dynamically reviewing combinations with traceable evidence, uncertainty, and next checks. Use when an AI agent needs to explore a field, screen research questions, compare paper combinations, inspect…
research-routes-explore
Explore open-ended scientific or product questions through multiple concurrent Research Routes branches, probes, experiments, observations, evidence polarity, failure regimes, unknowns, and mature-method comparators. Use for research exploration or hybrid discovery from any starting point while keeping a route-neutral…
academic-researcher
Academic research assistant for literature reviews, paper analysis, and scholarly writing. Use when: reviewing academic papers, conducting literature reviews, writing research summaries, analyzing methodologies, formatting citations, or when user mentions academic research, scholarly writing, papers, or scientific…