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/paper-statusnpx skills add matthewdigiuseppe/MStack --skill paper-statusgit clone --depth 1 https://github.com/matthewdigiuseppe/MStackWrote 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/matthewdigiuseppe/mstack/paper-status)<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/paper-status"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/paper-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 | $0.00074 | $0.00843 |
| Opus 5 | $0.00037 | $0.00421 |
| Sonnet 5 | $0.00015 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
paper-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 4d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:paper-status
Stage: power (any time) Voice: project-manager
When to invoke
Opening a session on an existing paper. Returning after a gap. Whenever the user asks "where were we?", "what's next?", or which skill to run. This skill is read-only apart from an offered paper.status correction.
Procedure
-
Locate the paper folder. Find
.mstack/in the current directory or an ancestor. If none exists, say so and suggest/mstack:mstack-init. -
Read
.mstack/config.yaml— title,paper.status, format,design.prereg, target journals. -
Inventory the pipeline. For each stage, check its artifacts and pull the verdict line (grep for
Verdict) plus the file date:Stage Artifacts to check Ideate .mstack/research-question.md,idea-shotgun-*.md,scope-challenge-*.mdMap .mstack/lit-map.md,theory.md,hypotheses.md,identification-review-*.mdDesign .mstack/design-research.md,power-analysis.md,survey-design.md,prereg/osf-prereg.mdBuild data/raw/PROVENANCE.md,data/clean/analytic.rds,data/codebook.mdAnalyze code/02-analyze.R,output/tables/*.tex,.mstack/results-audit-*.md,robustness-*.md,output/figures/*Write non-stub `paper/sections/*.tex Submit .mstack/journal-fit-*.md,submission/cover-letter.md,submission/response-to-reviewers/*Reflect .mstack/retro.md,replication-manifest.txt -
Flag staleness. A verdict is stale when its inputs changed after it was written — e.g. a results-audit older than
code/02-analyze.R, or an identification review older thanmethods.tex. Compare file modification times and flag each stale verdict for a re-run. -
Reconcile
paper.status. Derive the stage from the artifacts (the furthest stage with substantive output). If it disagrees withpaper.statusin config, say so and offer to update the field.
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.
- 4d ago First seen · 59 lines · 74 tokens per session scan A ccac5d118c1b
paper-status is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 843 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…