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 jurisdiction-formatgit 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/jurisdiction-format)<a href="https://agentmods.dev/skills/wanshuiyin/auto-claude-code-research-in-sleep/jurisdiction-format"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/jurisdiction-format/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/jurisdiction-format"><img src="https://agentmods.dev/badge/skills/wanshuiyin/auto-claude-code-research-in-sleep/jurisdiction-format.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.00047 | $0.01689 |
| Opus 5 | $0.00023 | $0.00844 |
| Sonnet 5 | $0.00009 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
jurisdiction-format 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 13d 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
2 near-identical copies found in the catalogue:
- jurisdiction-format — 100% identical, 2 lines differ
- jurisdiction-format — 89% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jurisdiction Format: Patent Filing Compilation
Compile the patent application into filing-ready format based on: $ARGUMENTS
Analogous to /paper-compile but for patent document formatting instead of LaTeX.
Constants
JURISDICTION = "auto"— From pipeline or args:CN,US,EP,ALLPATENT_TYPE = "invention"—invention(发明专利) orutility_model(实用新型, CN only)OUTPUT_FORMAT = "markdown"—markdown(for review) ordocx(for filing, requires python-docx)OUTPUT_DIR = "patent/output/"— Base output directory
Inputs
patent/CLAIMS.md— drafted claimspatent/specification/— all specification sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract)patent/figures/— figure descriptions and numeral indexpatent/INVENTION_DISCLOSURE.md— for metadata
Shared References
Load ../shared-references/patent-format-cn.md for CNIPA document structure and formatting rules.
Load ../shared-references/patent-format-us.md for USPTO document structure.
Load ../shared-references/patent-format-ep.md for EPO document structure.
Workflow
Step 1: Determine Output Jurisdictions
From $ARGUMENTS or constant:
CN-> Generate CNIPA format onlyUS-> Generate USPTO format onlyEP-> Generate EPO format onlyALL-> Generate all three formats
Step 2: Generate CN Format (if CN or ALL)
Output to patent/output/CN/:
权利要求书 (Claims)
- Extract claims from
patent/CLAIMS.md - Format per CNIPA conventions:
- Independent claims: "1. 一种[主题]的方法，...其特征在于..."
- Dependent claims: "2. 根据权利要求1所述的方法，其特征在于..."
- Ensure Chinese terminology is correct (所述, 其特征在于, 包括, 等)
说明书 (Description)
Combine all specification sections in CNIPA order:
- 发明名称 (from title.md)
- 技术领域 (from technical_field.md)
- 背景技术 (from background.md)
- 发明内容 (from summary.md — split into 技术问题/技术方案/有益效果)
- 附图说明 (from drawings_description.md)
- 具体实施方式 (from detailed_description.md)
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.
- 13d ago First seen · 193 lines · 47 tokens per session scan A 7683f58c4ad6
jurisdiction-format 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 47 tokens to every session and 1,689 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-30.
Other skills, from other repositories
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
paper-figures
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the extract-figures script as {{EXTRACTFIGURES}} — use…
legal-writer
Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…
employment-contract-templates
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.