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 matthewdigiuseppe/MStack --skill coauthor-reviewgit 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/coauthor-review)<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/coauthor-review"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/coauthor-review.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.00068 | $0.00810 |
| Opus 5 | $0.00034 | $0.00405 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
coauthor-review 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:coauthor-review
Stage: write Voice: coauthor
When to invoke
You have a complete draft, ideally one round before /mstack:referee-mock. The coauthor catches structural and clarity issues that a referee would gloss past or that you'd internalize too deeply to see.
Argument
$ARGUMENTS (optional) — coauthor persona. One of:
skeptical-methodologist(default) — challenges design and inference, line by line.big-picture-theorist— challenges the framing, contribution, and engagement with theory.junior-reader— reads as a graduate student new to the area; flags every "wait, what?".
If unrecognized, default to skeptical-methodologist.
Procedure
-
Load.
paper/main.texand everypaper/sections/*.tex. Read prior/mstack:coauthor-reviewoutputs in.mstack/referee-cache/so you can reference what changed since. -
Read end-to-end. Resist the urge to summarize. The first read is for impressions, not corrections.
-
Three structural notes (always):
- The biggest hole. One paragraph: where the argument is weakest. Quote the specific section.
- The biggest distraction. One paragraph: what to cut. Often a section the user is proudest of.
- The biggest opportunity. One paragraph: a missing argument, framing, or analysis that would land the paper better. Specific.
-
One structural suggestion. A concrete reordering, restructuring, or refocusing. Don't propose ten changes; propose one that changes the most.
-
Three to five line edits. Quote the line, give the alternative, explain in five words why.
-
Persona-specific bias:
Persona Where to press skeptical-methodologistIdentification, sample, SE, robustness, overclaiming in resultsanddiscussion.big-picture-theoristTheory section's mechanism, scope conditions, engagement with canonical work, contribution clarity. junior-readerWhere the reader gets lost. Jargon. Unexplained acronyms. Buried claims. Roadmap clarity.
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.
- 8d ago First seen · 71 lines · 68 tokens per session scan A 897132e588f4
coauthor-review is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 11d ago), licensed MIT. It adds 68 tokens to every session and 810 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…