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 skills add dtunai/agent-skills-for-compute --skill autoresearch-setupgit clone --depth 1 https://github.com/dtunai/agent-skills-for-computeWrote 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/dtunai/agent-skills-for-compute/autoresearch-setup)<a href="https://agentmods.dev/skills/dtunai/agent-skills-for-compute/autoresearch-setup"><img src="https://agentmods.dev/badge/skills/dtunai/agent-skills-for-compute/autoresearch-setup/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/skills/dtunai/agent-skills-for-compute/autoresearch-setup"><img src="https://agentmods.dev/badge/skills/dtunai/agent-skills-for-compute/autoresearch-setup.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.00043 | $0.02033 |
| Opus 5 | $0.00022 | $0.01017 |
| Sonnet 5 | $0.00009 | $0.00407 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
autoresearch-setup 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 10d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autoresearch Setup
Generate a complete autonomous research loop for any domain. Based on the autoresearch philosophy: an AI agent modifies code, runs experiments on a fixed budget, keeps or discards based on a single metric, and repeats indefinitely.
When to use: User wants to set up autonomous experimentation for ML training, kernel optimization, prompt engineering, hyperparameter search, or any domain where iterative improvement can be measured by a single metric.
Core Philosophy
- Single mutable file — the agent only edits ONE file. Everything else is fixed.
- Fixed time budget — every experiment runs for the same wall-clock time, making results directly comparable.
- Single metric — one number decides keep/discard. Lower or higher, pick one direction.
- program.md as research org code — the human writes strategy in Markdown, not Python. The agent interprets and executes.
- Git-backed experiments — every change is a commit. Keep = advance branch. Discard = reset.
- Results in TSV — plain text, human-readable, machine-parseable.
- Never stop — the agent runs autonomously until manually interrupted.
- Simplicity criterion — if equal performance, simpler code wins. Ugly complexity for tiny gains is not worth it.
Setup Flow
When the user asks to set up autoresearch for a given context, follow these steps:
Step 1: Understand the Domain
Ask or infer:
- What is being optimized? (model architecture, kernel, prompt, config, algorithm...)
- What is the metric? (loss, accuracy, throughput, latency, score...)
- Metric direction? (lower is better / higher is better)
- Time budget per experiment? (default: 5 minutes)
- What hardware/environment? (GPU, CPU, cloud, local...)
- What are the fixed constraints? (data, evaluation, dependencies)
Step 2: Generate Project Structure
Create this structure in the target directory:
<project>/
├── program.md — Agent instructions (human-edited strategy)
├── prepare.py — Fixed: data prep, evaluation, constants (DO NOT MODIFY)
├── experiment.py — Mutable: the file the agent edits (ONLY THIS FILE)
├── results.tsv — Experiment log (git-ignored)
├── pyproject.toml — Dependencies (locked)
└── .gitignore — Ignores results.tsv, run.log, __pycache__
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.
- 10d ago First seen · 251 lines · 43 tokens per session scan A a351cd31b398
autoresearch-setup is a skill published in the GitHub repository dtunai/agent-skills-for-compute (2 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 2,033 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…