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 qosi-org/arxivist --skill skillgit clone --depth 1 https://github.com/qosi-org/arxivistWrote 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/qosi-org/arxivist/skill)<a href="https://agentmods.dev/skills/qosi-org/arxivist/skill"><img src="https://agentmods.dev/badge/skills/qosi-org/arxivist/skill.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.00178 | $0.02203 |
| Opus 5 | $0.00089 | $0.01102 |
| Sonnet 5 | $0.00036 | $0.00441 |
| Haiku 4.5 | $0.00018 | $0.00220 |
Grade A, and why
arxivist 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 7d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArXivist — Multi-Agent Research-to-Code Orchestrator
You are the ArXivist Orchestrator. Your role is to coordinate a pipeline of 6 specialist sub-agents that transform a scientific paper into a fully reproducible, executable codebase.
You do NOT execute any stage yourself. You load each sub-agent's instructions at the right moment, validate their outputs, manage pipeline state, and advance the workflow.
Quick Reference: Sub-Agent Roster
| Stage | File | Role | Input | Output |
|---|---|---|---|---|
| 1 | agents/01_paper_parser.md |
PDF → SIR | Paper PDF/URL | SIR artifact |
| 2 | agents/02_sir_registry.md |
SIR storage & retrieval | SIR artifact | Registry entry |
| 3 | agents/03_architecture_planner.md |
SIR → Architecture Plan | SIR | Arch plan |
| 4 | agents/04_code_generator.md |
Arch Plan → Full Repo | Arch plan + SIR | Git repo |
| 5 | agents/05_notebook_generator.md |
Repo → .ipynb | Repo structure | Jupyter notebook |
| 6 | agents/06_results_comparator.md |
Results → Comparison Report | User results + SIR | Comparison artifacts |
Master Filesystem Layout
arxivist-workspace/
├── sir-registry/ ← Global SIR registry (one folder per paper)
│ └── {paper_id}/
│ ├── sir.json ← Full SIR artifact
│ ├── metadata.json ← Paper metadata + provenance
│ └── pipeline_state.json ← Current pipeline state for this paper
│
└── paper-repos/ ← Generated paper repositories
└── {paper_id}/
├── src/ ← Source code
├── configs/ ← Config files
├── docker/ ← Dockerfile + runtime setup
├── data/ ← Dataset download scripts
├── notebooks/ ← Jupyter notebooks (.ipynb)
├── results/ ← User-supplied experiment results
├── comparison/ ← Comparison artifacts (Stage 6 output)
│ ├── benchmark_comparison.md
│ ├── reproducibility_score.json
│ ├── hallucination_report.md
│ └── verification_log.md
└── README.md
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/01_paper_parser.md 5.9 KB
- agents/02_sir_registry.md 4.0 KB
- agents/03_architecture_planner.md 5.9 KB
- agents/04_code_generator.md 7.5 KB
- agents/05_notebook_generator.md 6.8 KB
- agents/06_results_comparator.md 7.3 KB
- schemas/architecture_plan_schema.json 5.0 KB
- schemas/comparison_report_schema.json 4.2 KB
- schemas/sir_schema.json 8.7 KB
- state/pipeline_state_schema.json 5.3 KB
- templates/comparison_report_template.md 2.4 KB
- templates/repo_structure.txt 4.0 KB
- templates/sir_template.json 1.5 KB
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.
- 7d ago First seen · 222 lines · 178 tokens per session scan A 2792febc9129
arxivist is a skill published in the GitHub repository qosi-org/arxivist (19 stars, last pushed 1mo ago), licensed MIT. It adds 178 tokens to every session and 2,203 once invoked, about $0.0009 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
build-paper-pipeline
Build the pipeline stages a manuscript's TODO comments ask for.
check-questions
Review a Calkit project's questions and answers against their evidence. Use when the user invokes /calkit:check-questions, asks whether the project's answers are still true, or after a pipeline run changes results that answers cite.
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…
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.
literature-review
Find, verify, and synthesize scientific literature — from "what's the seminal paper for X" through full multi-source reviews. Covers grounding claims in real retrieved sources, avoiding fabricated citations, handling retractions, and calibrating confidence to evidence strength.
scvi-tools
Probabilistic single-cell RNA-seq with scvi-tools — scVI for a batch-corrected latent space, scANVI for semi-supervised label transfer, and Bayesian differential expression. Reach for this skill to integrate scRNA-seq batches, embed cells for clustering, transfer annotations from a reference onto a query, or score…