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 hdu-ailab/EasyResearch --skill autoresearchgit clone --depth 1 https://github.com/hdu-ailab/EasyResearchWrote 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/hdu-ailab/easyresearch/autoresearch)<a href="https://agentmods.dev/skills/hdu-ailab/easyresearch/autoresearch"><img src="https://agentmods.dev/badge/skills/hdu-ailab/easyresearch/autoresearch/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/hdu-ailab/easyresearch/autoresearch"><img src="https://agentmods.dev/badge/skills/hdu-ailab/easyresearch/autoresearch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 19 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00053 | $0.01625 |
| Opus 5 | $0.00026 | $0.00813 |
| Sonnet 5 | $0.00011 | $0.00325 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
autoresearch 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autoresearch
Purpose
Turn one explicit user authorization into a sustained, metric-driven research campaign. Auto means the campaign keeps making valid experimental progress without asking for routine approval after every trial. It does not mean unbounded cost, unsafe mutation, metric hacking, or bypassing formal evidence requirements.
This Skill is orchestration-only. The Research Assistant defines and monitors the campaign, while one Experiment specialist owns all code changes, commands, metrics, rollback, and experiment artifacts. The Research Assistant must never perform those specialist actions itself.
Activation Contract
Treat an explicit auto/autoresearch/overnight/until-stopped request as approval for one exploratory campaign within an inspectable contract. Derive values from the user's request and existing project artifacts before asking anything.
The contract must name:
| Field | Requirement |
|---|---|
| Objective | One measurable experimental question |
| Selection metric | Primary validation metric and maximize/minimize direction |
| Evaluation boundary | Immutable evaluator, split, preprocessing, and anti-leakage rules |
| Mutable scope | Exact files or directories the Experiment specialist may change |
| Immutable scope | Evaluation harness, final-test data, source evidence, and protected files |
| Trial command | Reproducible command plus per-trial timeout |
| Budget | Trial count, wall-clock/compute budget, or explicit until-stopped authorization |
| Acceptance rule | Improvement threshold and simplicity/resource tie-breaker |
| Recovery | Snapshot and rollback method limited to mutable scope |
| Artifacts | Exact campaign, ledger, log, output, and summary paths |
Ask at most one focused question only when a safety-, cost-, or decision-critical field cannot be derived. Never invent a metric or silently authorize open-ended paid compute. An explicit until-stopped request is valid only on compute the user has already authorized.
Default Artifact Contract
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 · 176 lines · 53 tokens per session scan A d333d9e53f5f
autoresearch is a skill published in the GitHub repository hdu-ailab/EasyResearch (13 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,625 once invoked, about $0.0003 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
ai-research-reproduction
Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted…
ai-research-explore
Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of currentresearch with auditable repo…
explore-run
Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with…
analyze-project
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or…
env-and-assets-bootstrap
Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full…
safe-debug
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research…