ARIS is a collection of Markdown-based skills that define a workflow for autonomous machine-learning research, including idea discovery, experiment automation, and review loops. Researchers and AI coding agents use it across tools such as Claude Code, Codex, Cursor, and OpenClaw without depending on a single framework. The catalogue entries are ARIS workflow skills and agents.
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 wanshuiyin/Auto-claude-code-research-in-sleep --skill resubmit-pipelinegit clone --depth 1 https://github.com/wanshuiyin/Auto-claude-code-research-in-sleepWrote 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/wanshuiyin/auto-claude-code-research-in-sleep/resubmit-pipeline)<a href="https://agentmods.dev/skills/wanshuiyin/auto-claude-code-research-in-sleep/resubmit-pipeline"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/resubmit-pipeline/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/wanshuiyin/auto-claude-code-research-in-sleep/resubmit-pipeline"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/resubmit-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00103 | $0.08548 |
| Opus 5 | $0.00051 | $0.04274 |
| Sonnet 5 | $0.00021 | $0.01710 |
| Haiku 4.5 | $0.00010 | $0.00855 |
Grade A, and why
resubmit-pipeline 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resubmit-pipeline — 94% identical, 34 lines differ
How it starts
The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resubmit Pipeline: Text-Only Microedit Mode
Compose a polished paper into a new venue under text-only constraints: $ARGUMENTS
Why This Exists
Most ARIS writing workflows assume the input is either a narrative report (Workflow 3) or an in-progress paper that may still need experiments / bib changes / structural edits. Resubmit is a fundamentally different scope:
- The paper is already polished — proofs are done, experiments are done, bibliography is curated.
- The user wants to absorb prior reviewer concerns from a previous venue and re-submit, without introducing new experiments, new citations, or framework changes (LLM hallucination paranoia + tight resubmit timing + closed compute budget).
- The base submission directory is read-only — the new submission must compose into a sibling directory, never mutate prior state.
- Page limit may shrink between source and target venue (e.g., workshop camera-ready → 9-page main).
Existing skills cover adjacent territory but none of this exact composition: /rebuttal builds the OpenReview-style response document, not in-paper microedits; /auto-paper-improvement-loop is the per-round engine but presupposes someone has already chosen the base manuscript, migrated venue format, set the edit whitelist, queued the reviewer feedback, and decided what NOT to change. /resubmit-pipeline fills that orchestration gap.
When to Use
- A theory or system paper was rejected at venue A and you want to resubmit to venue B with tight time budget (≤ 1-2 weeks).
- You have 3 inputs ready: the polished paper directory at venue A's format, the target venue B's format/template/style files, and the prior reviewer reports.
- You explicitly do not want to re-derive theorems, run new experiments, or change the bibliography.
When NOT to Use
- The paper still needs experiments — use
/experiment-bridge→/auto-review-loopfirst. - The paper still needs structural rewrites or new sections — use
/paper-writing(Workflow 3). - You want to write the rebuttal response itself — use
/rebuttal(Workflow 4). - The reviewer feedback demands new theorems or new framework — escalate to user before starting; this skill emits
BLOCKEDwithreason_code: out_of_scope_microeditif it detects this case.
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.
- 5d ago Changed 4fa03710fe1f
- 9d ago First seen · 448 lines · 103 tokens per session scan A c919caf4c1df
resubmit-pipeline is a skill published in the GitHub repository wanshuiyin/Auto-claude-code-research-in-sleep (16,030 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 8,548 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
remote-compute-ssh
Evaluate and use SSH Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote commands and asynchronous jobs with automatic harvest and analysis.
figure-style
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots. Use for a figure that will ship in a report, paper, export, or kept artifact. Covers data fidelity, label economy, color threading, chart choice, layout, and render-then-verify QA without imposing a…
evo2
Score, embed, and generate DNA sequences with Evo 2, a long-context genomic foundation model. Use this skill when: (1) Computing per-nucleotide or per-sequence likelihoods for variant effect scoring, (2) Embedding genomic windows for downstream classification, (3) Generating DNA conditioned on a prefix, (4) Scoring…
ligandmpnn
Inverse-fold a backbone with ligand, nucleic-acid, and metal context using LigandMPNN (Dauparas et al. 2023, github.com/dauparas/LigandMPNN). Reach for this skill to redesign the residues lining a binding pocket around a bound small molecule or cofactor, to design metal-coordinating sites where the geometry must be…
memory
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
ml-training-recipes
Battle-tested PyTorch training recipes for all domains — LLMs, vision, diffusion, medical imaging, protein/drug discovery, spatial omics, genomics. Covers training loops, optimizer selection (AdamW, Muon), LR scheduling, mixed precision, debugging, and systematic experimentation. Use when training or fine-tuning…