AutoSci is an AI research platform organized around a wiki, with an agent that supports stages of scientific work such as reading, experimentation, writing, and retaining knowledge across projects. It is for people building or using AI-assisted research workflows, with Claude Code, Codex, and OpenCode adaptations available. The catalogue add-ons extend those agent-specific workflows.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skyllwt/autosci/exp-status)<a href="https://agentmods.dev/skills/skyllwt/autosci/exp-status"><img src="https://agentmods.dev/badge/skills/skyllwt/autosci/exp-status.svg" alt="Measured on agentmods" 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.00018 | $0.02399 |
| Opus 5 | $0.00009 | $0.01200 |
| Sonnet 5 | $0.00004 | $0.00480 |
| Haiku 4.5 | $0.00002 | $0.00240 |
Grade A, and why
exp-status 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 6d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/exp-status
Unified experiment status monitoring entry point. Scans all
runningexperiments, performs a live status check on each (screen session / SSH), and outputs a status table (alive / anomaly / completed) to guide the user's next actions.When used with
/research --auto, acts as a periodic checker scheduled by CronCreate: when all experiments in a pipeline are completed, automatically triggers/research --start-from stage4.
Inputs
- No arguments (default): check all
runningexperiments, print status table --pipeline <slug>(optional): check only experiments belonging to the specified pipeline; additionally print overall pipeline progress--collect-ready(optional): auto-call/exp-run --collectfor all experiments whose session has already ended--auto-advance(optional, requires--pipeline <slug>): if all pipeline experiments arecompleted, automatically trigger/research --start-from stage4without waiting for the user
Outputs
- Status report (terminal output, all modes): list of experiments in running/anomaly/completed states
wiki/experiments/{slug}.md— updated (outcome/key_result/status) when--collect-readytriggers Phase 4wiki/outputs/pipeline-progress.md—--auto-advanceupdates current_stage → stage4 (done internally by /research --start-from stage4)wiki/log.md— appended status check log
Wiki Interaction
Reads
wiki/experiments/*.md— status, remote frontmatter (server/session/started), date_plannedwiki/outputs/pipeline-progress.md— in--pipelinemode, identifies target experiments and monitoring_cron_id
Writes
wiki/experiments/{slug}.md— updated via /exp-run --collect in--collect-readymodewiki/outputs/pipeline-progress.md— updated by /research when--auto-advancetriggers Stage 4wiki/log.md— appended status check log
Graph edges created
- None (result writes triggered indirectly via /exp-run --collect do not produce new edges)
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.
- 6d ago First seen · 230 lines · 18 tokens per session scan A cb61eac1770d
exp-status is a skill published in the GitHub repository skyllwt/AutoSci (1,660 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 2,399 once invoked, about $0.0001 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
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…