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/survey)<a href="https://agentmods.dev/skills/skyllwt/autosci/survey"><img src="https://agentmods.dev/badge/skills/skyllwt/autosci/survey.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.00030 | $0.02419 |
| Opus 5 | $0.00015 | $0.01210 |
| Sonnet 5 | $0.00006 | $0.00484 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
survey 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/survey
Generate a Related Work section ready for direct use in a paper, based on existing wiki knowledge. Draw material from wiki/papers/, concepts/, topics/; group by research direction (not paper-by-paper listing). End each group with a statement of how it differs from this work. Citations follow citation-verification.md; writing follows academic-writing.md Related Work rules. Supports LaTeX and Markdown output formats.
Inputs
query: one of:- research question description (free text, e.g. "parameter-efficient fine-tuning for LLMs")
- list of idea slugs (from wiki/ideas/, used to organize related work around specific ideas)
- path to PAPER_PLAN.md (extract Related Work section definition from it)
--format(optional, defaultlatex): output formatlatex:\cite{key}citations, embeddable directly in a papermarkdown:[[slug]]wikilink citations, for wiki archiving
--max-papers(optional, default 30): maximum number of papers to cite
Outputs
wiki/outputs/related-work-{slug}-{date}.md— Related Work text (archived)wiki/graph/edges.jsonl— derived_from edges (if a new output is created)wiki/log.md— appended log entry- Terminal output — Related Work body text (for direct copy-paste)
Wiki Interaction
Reads
wiki/papers/*.md— Problem & Context, Key idea, Experiment & Results, Related, My takewiki/concepts/*.md— Definition, Variants, Comparison, Known limitationswiki/topics/*.md— Overview, Timeline, Open problems, Seminal workswiki/ideas/*.md— Hypothesis, Motivation, origin_gaps (if input is idea slugs)wiki/methods/*.md— Mechanism, Procedure, source_papers (when ideas reference methods)wiki/index.md— content catalog, filtered by importancewiki/graph/context_brief.md— global contextwiki/graph/edges.jsonl— inter-paper semantic relationships (same_problem_as, similar_method_to, builds_on, challenges).claude/skills/shared-references/academic-writing.md— Related Work writing rules.claude/skills/shared-references/citation-verification.md— citation discipline
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 · 217 lines · 30 tokens per session scan A 1c1919f457aa
survey is a skill published in the GitHub repository skyllwt/AutoSci (1,660 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 2,419 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…