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/submission-packnpx skills add matthewdigiuseppe/MStack --skill submission-packgit 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/submission-pack)<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/submission-pack"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/submission-pack.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.00070 | $0.00985 |
| Opus 5 | $0.00035 | $0.00492 |
| Sonnet 5 | $0.00014 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
submission-pack 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:submission-pack
Stage: submit Voice: production-editor
When to invoke
After /mstack:journal-fit picks the journal and the manuscript is final. Everything else in MStack front-runs the reviewers; this skill front-runs the desk — the mechanical checks (anonymity, word count, formatting) that get papers bounced before anyone reads them.
Argument
$ARGUMENTS (optional) — the journal to pack for. Defaults to the tier-1 journal in .mstack/config.yaml.
Procedure
-
Establish the journal's requirements. WebFetch the journal's author guidelines, or ask the user for them; never trust memory for word caps, anonymization policy, abstract limits, or reference style — they change. Record: word cap (and what counts toward it), abstract cap, double-blind y/n, figure/table placement rules, reference style, supplementary-material policy.
-
Anonymization sweep (double-blind journals):
- Grep
paper/for every author name and affiliation from.mstack/config.yaml. - Find self-identifying citations — "our previous work", "as we showed (Name YEAR)" — and recast in third person or as "Author (YEAR)" per the journal's convention. Never delete the citation itself; that breaks the argument.
- Strip or fence acknowledgments, thanks, grant numbers, IRB protocol numbers tied to an institution, and
\thanks{}/\author{}content into a separatepaper/title-page.texthat is NOT part of the anonymized build. - Note PDF metadata: the compiled anonymized PDF must not carry author names in its document properties.
- Grep
-
Compliance checks:
- Word count vs. the cap (
texcount main.tex -inc -totalif available; otherwise a documented approximation) — state the count and the margin. - Abstract length vs. the abstract cap.
- Reference style vs. what the bibliography actually produces.
- Figures/tables: count, placement (embedded vs. end-of-manuscript), and resolution requirements.
- Word count vs. the cap (
-
Build the bundle. Compile the anonymized manuscript and the title page separately (
latexmk/pdflatex, orquarto render; if no TeX toolchain is available, stage the sources and list the manual compile steps). Stage everything undersubmission/<journal-slug>/: anonymized PDF, title page, figures at spec, supplementary material, and the prereg URL ifdesign.preregis true.
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.
- 5d ago First seen · 67 lines · 70 tokens per session scan A 9659c49d0b8c
submission-pack is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 8d ago), licensed MIT. It adds 70 tokens to every session and 985 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
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…