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/preregisternpx skills add matthewdigiuseppe/MStack --skill preregistergit 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.00077 | $0.01070 |
| Opus 5 | $0.00039 | $0.00535 |
| Sonnet 5 | $0.00015 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
preregister 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:preregister
Stage: design Voice: preregistration-clerk
When to invoke
Before fielding a survey, before running a secondary-data analysis on a sample you haven't touched, or before any design where you want to credibly distinguish confirmatory from exploratory analysis.
Procedure
-
Load context.
.mstack/research-question.md,.mstack/lit-map.md,.mstack/identification-review-*.md..mstack/survey-design.mdif a survey is involved.paper/sections/theory.texandmethods.texif drafted.
-
Pick a registry. Default to OSF; AsPredicted if the design is small (≤ 9-section format). Note the choice in the document header.
-
Draft
prereg/osf-prereg.md— start from the bundled skeleton at${CLAUDE_PLUGIN_ROOT}/skills/preregister/assets/prereg-template.md— with these sections, all required:1. Hypotheses
List H1, H2, … with direction and effect size sign. State which is primary; secondaries are explicitly secondary.
2. Sample
- Population.
- Recruitment source (Prolific, MTurk, panel name, observational frame).
- Target N. Justification =
/mstack:power-analysisoutput. - Stopping rule: time-bound, N-bound, or both.
3. Exclusions
List every exclusion rule with a threshold, decided before seeing data. From
survey-design.mdprobe manifest if applicable.4. Measures
- Independent variable(s) — definition, source, scale.
- Dependent variable(s) — definition, source, scale, scoring rule.
- Covariates — what is controlled for, why.
5. Primary analysis
The one specification that tests H1. State equation, sample, SE clustering, software, and the rejection rule (e.g., two-sided test at α = 0.05).
6. Secondary analyses
Pre-specified secondaries and any planned heterogeneity / moderation tests.
7. Robustness
List the robustness checks committed to in advance (e.g., alternative samples, alternative operationalizations, alternative SE structures).
What ships with it
1 file 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.
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 · 91 lines · 77 tokens per session scan A 58eae3aa9336
preregister is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 1,070 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.