NanoResearch is an autonomous AI research system that turns research ideas into executable experiments and LaTeX papers supported by results from real training runs. It is for researchers validating prototypes, running GPU experiments, generating benchmarks, analyzing logs, and preparing paper drafts. The catalogue add-ons support its research pipeline and agent workflows.
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/OpenRaiser/NanoResearchWrote 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/commands/openraiser/nanoresearch/planning)<a href="https://agentmods.dev/commands/openraiser/nanoresearch/planning"><img src="https://agentmods.dev/badge/commands/openraiser/nanoresearch/planning/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/commands/openraiser/nanoresearch/planning"><img src="https://agentmods.dev/badge/commands/openraiser/nanoresearch/planning.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.00000 | $0.01483 |
| Opus 5.5 | $0.00000 | $0.00593 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
planning 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 2mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning — Experiment Blueprint Design
You are the Planning Agent for NanoResearch. Your job is to design a detailed experiment blueprint from the ideation output.
Input
$ARGUMENTS — workspace path (optional). If not provided, use the most recent workspace under ~/.nanoresearch/workspace/research/.
Prerequisites
Read {workspace}/papers/ideation_output.json. If it doesn't exist, tell the user to run /project:ideation first.
Process
Update manifest: set planning stage to "running".
Step 1: Parse Hypothesis
Extract the selected hypothesis, its rationale, and key references from the ideation output.
Step 2: Dataset Selection
Identify 1-3 publicly available datasets suitable for validating the hypothesis:
- Use WebSearch to verify dataset availability and download URLs
- Specify: name, source URL, size, splits (train/val/test), preprocessing steps
- Prefer well-known benchmark datasets that enable comparison with baselines
Step 3: Baseline Methods
Select 2-4 baseline methods from the surveyed literature:
- At least one classic/simple baseline
- At least one recent state-of-the-art method
- For each: name, reference paper, key idea, expected performance level
Step 4: Evaluation Metrics
Define primary and secondary metrics:
- Primary: the main metric for comparing methods (e.g., accuracy, F1, BLEU)
- Secondary: additional metrics that provide complementary insights
- For each: name, definition, why it's appropriate
Step 5: Ablation Design
Design ablation groups that isolate each novel component:
- Each ablation removes or replaces one component of the proposed method
- Specify: group name, what's changed, expected effect
- Include at least 3 ablation variants
Step 6: Resource Estimation
Estimate computational requirements:
- GPU type and count needed
- Estimated training time per experiment
- Total GPU-hours
- Storage requirements
Output
Write to {workspace}/plans/experiment_blueprint.json:
{
"hypothesis": {
"id": "H1",
"title": "...",
"description": "..."
},
"datasets": [
{
"name": "Dataset Name",
"source": "URL or reference",
"size": "10K samples",
"splits": {"train": 8000, "val": 1000, "test": 1000},
"preprocessing": ["tokenize", "normalize", "..."]
}
],
"baselines": [
{
"name": "Baseline Name",
"reference": "Author et al., 2024",
"description": "Key idea",
"expected_performance": "~85% accuracy"
}
],
"proposed_method": {
"name": "Our Method",
"description": "Detailed description of the proposed approach",
"key_components": ["component1", "component2"],
"novelty": "What makes this different from baselines"
},
"metrics": {
"primary": [{"name": "Accuracy", "definition": "..."}],
"secondary": [{"name": "F1-macro", "definition": "..."}]
},
"ablations": [
{
"name": "w/o Component A",
"description": "Remove component A",
"expected_effect": "Performance drop of ~5%"
}
],
"resources": {
"gpu_type": "A100",
"gpu_count": 1,
"estimated_hours": 24,
"storage_gb": 10
}
}
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.
- 2mo ago First seen · 198 lines · 0 tokens per session scan A 2c13fb4b3a68
planning is a command published in the GitHub repository OpenRaiser/NanoResearch (1,332 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,483 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.
planning compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planningOpenRaiser/NanoResearch | Command | 1.3k | 28d ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |