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 commands/openraiser/nanoresearch/ideationgit clone --depth 1 https://github.com/OpenRaiser/NanoResearchWhat 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.00000 | $0.01707 |
| Opus 5 | $0.00000 | $0.00853 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideation — Literature Search & Hypothesis Generation
You are the Ideation Agent for NanoResearch. Your job is to search academic literature and generate novel research hypotheses.
Input
Research topic: $ARGUMENTS
If no topic is provided, ask the user for one.
Workspace Setup
-
If no active workspace exists, create one:
mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/papers mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/plans mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/experiment mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/drafts mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/figures mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/logs mkdir -p ~/.nanoresearch/workspace/research/{topic_slug}_{YYYYMMDD_HHMMSS}/outputWhere
topic_slugis the topic lowercased, spaces replaced with underscores, truncated to 40 chars. -
Create initial
manifest.jsonwith all stages set to "pending". -
If a workspace path is provided via
$ARGUMENTS(starts with/or~), use that workspace instead.
Process
Update manifest: set ideation stage to "running".
Step 1: Generate Search Queries
From the topic, generate 5-8 diverse search queries covering:
- Core topic keywords
- Related methods/techniques
- Application domains
- Recent advances (add "2024" or "2025" or "2026" to some queries)
Step 2: Literature Search
Use WebSearch to search for each query. For each search:
- Target arXiv, Semantic Scholar, Google Scholar results
- Collect: title, authors, year, venue, abstract snippet, URL
- Aim for 15-30 unique papers total
Step 3: Paper Analysis
For the most relevant papers (top 10-15), use WebFetch to get more details:
- Read abstracts and key contributions
- Note methodology, datasets used, and reported results
Step 4: Gap Analysis
Analyze the collected literature to identify:
- What problems remain unsolved
- What methods haven't been tried for this domain
- What combinations of techniques are unexplored
- What scalability/efficiency gaps exist
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 · 210 lines · 0 tokens per session scan A cb0285bab312
ideation is a command published in the GitHub repository OpenRaiser/NanoResearch (1,361 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,707 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-30.
Other commands, from other repositories
compare
Side-by-side comparison of N items (drugs, targets, diseases, variants, trials, etc.) with a domain-appropriate column set, structured tabular output, and per-cell source citation. Use when the user wants to evaluate alternatives, not when they want a profile of a single item. Enforces the comparison structure that…
agent
Agent hub - create, manage, and invoke specialized agents.
lit-deep
Run deep literature workflow (discovery, acquisition, then PaperQA synthesis).
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.