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 agentmods add skills/matthewdigiuseppe/mstack/archivenpx skills add matthewdigiuseppe/MStack --skill archivegit clone --depth 1 https://github.com/matthewdigiuseppe/MStackWhat 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 | $0.00061 | $0.01321 |
| Opus 5 | $0.00030 | $0.00660 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
archive 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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:archive
Stage: reflect (at acceptance) Voice: replicator
When to invoke
The paper is accepted. Before the journal sets the production deadline you forgot about, lock the replication package. The point is not to satisfy the journal's data policy — it's to ensure that two years from now you (or anyone else) can rebuild every table and figure from raw data.
Procedure
-
Load context.
.mstack/config.yamlfor paper title, target journal (now the actual journal).paper/,data/,code/,output/.prereg/if applicable.
-
Inventory. Walk the project and list:
- Raw data files in
data/raw/with sources, vintages, licenses. - Cleaned data file(s) in
data/clean/. - Code files in
code/, ordered by run order. - Output files in
output/(tables, figures, model objects). - Manuscript files (final accepted version).
- Preregistration documents.
.mstack/llm-usage.jsonlplus everyprompt_user_ref/code_reffile it names (GUIDE-LLM artifacts), if the ledger exists. Save the inventory toreplication-manifest.txt.
- Raw data files in
-
Check licenses. For each raw data file:
- Public-domain or open: include in the package.
- Restricted (e.g., commercial, IRB-restricted): replace with a stub + script that re-acquires from source. Document the restriction in the README.
Tag each file accordingly in
replication-manifest.txt.
-
Pin dependencies.
- R: capture
sessionInfo()and (preferred) generate arenv.lockviarenv::snapshot(). Addrenv/activate.Rso the package self-restores. - System dependencies: list in the README (e.g., LaTeX distribution, JAGS, Stan, GDAL).
- Quarto/LaTeX versions if relevant.
- R: capture
-
Extend
README.mdinto a replication README with:- One-paragraph paper summary + final citation.
- Layout (the standard MStack tree).
- Reproduction steps — run every numbered script, not a hardcoded four;
/mstack:codebook,/mstack:power-analysis, and/mstack:robustnessadd 00/05/06-series scripts whose outputs also ship:renv::restore() scripts <- sort(list.files("code", pattern = "^[0-9].*\\.R$", full.names = TRUE)) scripts <- scripts[!grepl("00-fetch", scripts)] # raw data ships in the package; fetch scripts hit the network for (f in scripts) source(f) - Mapping: which script produces which table / figure (a table indexed by
output/filename). - Data source documentation (one entry per raw file).
- Known divergences from the published paper (e.g., a figure that was hand-edited in Illustrator — flag the post-hoc edit).
- License (CC-BY for code unless user specifies otherwise; data licenses inherit from sources).
- Contact + DOI placeholder for the published paper.
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.
- 2d ago First seen · 97 lines · 61 tokens per session scan A 17604e2e7f2e
archive is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 1,321 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
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…
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…
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.