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 invention-structuringgit 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/invention-structuring)<a href="https://agentmods.dev/skills/wanshuiyin/auto-claude-code-research-in-sleep/invention-structuring"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/invention-structuring/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/invention-structuring"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/invention-structuring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- 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.00056 | $0.01473 |
| Opus 5 | $0.00028 | $0.00737 |
| Sonnet 5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
invention-structuring 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:
- invention-structuring — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invention Structuring
Structure the invention into a formal disclosure based on: $ARGUMENTS
Adapted from the refinement pattern in /research-refine for patent invention decomposition.
Constants
REVIEWER_MODEL = gpt-6-astra— External reviewer for invention decomposition validationMAX_REFINEMENT_ROUNDS = 3— Maximum structuring iterations
Inputs
- Invention description from
$ARGUMENTS patent/INVENTION_BRIEF.mdif existspatent/PRIOR_ART_REPORT.md— prior art landscapepatent/NOVELTY_ASSESSMENT.md— novelty analysis
Shared References
Load ../shared-references/patent-writing-principles.md for the Problem-Solution-Advantage framework and claimable subject matter guidelines.
Workflow
Step 1: Problem-Solution-Advantage Framework
Structure the invention using the universal patent framework:
Technical Problem (要解决的技术问题):
- Derived from prior art deficiencies identified in NOVELTY_ASSESSMENT.md
- Must be a specific, technical problem (not a commercial or social problem)
- Statement format: "The technical problem to be solved is how to [specific technical objective] given [specific technical constraint]."
Technical Solution (技术方案):
- The invention's specific technical contribution
- Focus on the mechanism, not the result
- Must be described at a level that matches the intended claim scope
- Identify which features are known vs. inventive
Advantages (有益效果):
- Measurable or quantifiable improvements over prior art
- Must result from the inventive features, not just good engineering
- Include specific technical effects if known (e.g., "reduces processing time by 40%")
Step 2: Invention Decomposition
Break the invention into three layers:
Core Inventive Concept (核心发明构思):
- The minimal set of features that make the invention patentable
- This maps to the independent claim scope
- Test: if you remove this feature, the invention is no longer novel
Supporting Features (支撑性特征):
- Features that make the invention work well in practice
- These become dependent claim material
- They narrow the scope but add practical value
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 ced6627e44e9
- 13d ago First seen · 189 lines · 56 tokens per session scan A bc0ac16349e9
invention-structuring 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 56 tokens to every session and 1,473 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
privacy-by-design
Use when building apps that collect user data. Ensures privacy protections are built in from the start—data minimization, consent, encryption.
ethics-committee
Act as a research ethics committee — stress-test a protocol the way an IRB / REC / HREC would. Reviews informed consent, risk-benefit balance, vulnerable populations, data privacy, deception, debriefing, payment, dual-use risks, AI/LLM use in research, and equity in recruitment. Produces a committee-style decision…
freelance-dev-sow
When to use. A potential client wants a fixed-scope software project and needs a one-page SOW before they sign + pay deposit.
advogado-especialista
Advogado especialista em todas as areas do Direito brasileiro: familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil e constitucional.
advogado-criminal
Advogado criminalista especializado em Maria da Penha, violencia domestica, feminicidio, direito penal brasileiro, medidas protetivas, inquerito policial e acao penal.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.