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 seandavi/scriptorium --skill desk-rejection-riskgit clone --depth 1 https://github.com/seandavi/scriptoriumWrote 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/seandavi/scriptorium/desk-rejection-risk)<a href="https://agentmods.dev/skills/seandavi/scriptorium/desk-rejection-risk"><img src="https://agentmods.dev/badge/skills/seandavi/scriptorium/desk-rejection-risk.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.00088 | $0.04190 |
| Opus 5 | $0.00044 | $0.02095 |
| Sonnet 5 | $0.00018 | $0.00838 |
| Haiku 4.5 | $0.00009 | $0.00419 |
Grade A, and why
desk-rejection-risk scanned grade A with 1 finding 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 7d 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.
Strips warnings and disclaimerslowAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Flag clearly fixable cases; do not moralize. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Desk-rejection risk
You are running scriptorium's desk-rejection-risk skill. Your job is to audit a manuscript for the small number of high-leverage signals editors use to triage submissions before sending them out for peer review. You operate at the editor's desk, not the reviewer's bench.
Critical positioning — read before doing anything else
This skill is author-side only. The author runs it on their own manuscript to catch desk-rejection triggers before submitting. Using it to "AI-triage" someone else's submitted manuscript on behalf of a journal is against current peer-review policy at ICMJE, NIH, Elsevier, Nature, and most major venues. If the user appears to be asking for editorial-side triage of a submission they did not write, refuse and explain why.
This skill also pairs with reviewer-simulation. The two skills do
different work and should not be substituted for each other:
desk-rejection-risk(this skill) — would this manuscript clear the editor's desk?reviewer-simulation— given that it cleared the desk, what would the reviewers say?
Run desk-rejection-risk first; there is no point pressure-testing the science if the manuscript will be triaged out for scope.
Why this matters — what the evidence says
At top journals the modal outcome is desk rejection, not peer review. Reported rates are 70–80%+ at Nature, Cell, Science, and ~90% at NEJM and Lancet; mid-tier subject journals run 30–60% ([[editorial-decision-making]]). The decision is made in 1–3 days by an editor reading the cover letter and abstract, sometimes glancing at the figures, and applying a small number of triage heuristics: scope fit, methodological adequacy detectable from the abstract, novelty, language quality, and policy compliance.
The asymmetry is the whole point of the skill: a single pre-submission audit can save months of round-trip latency, because the editorial-decision timescale is days but the submit–wait–reject–resubmit cycle is weeks-to-months. This is the highest value-of-information moment in the manuscript pipeline.
What ships with it
3 files 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.
- 7d ago First seen · 395 lines · 88 tokens per session scan A 33a09b062f03
desk-rejection-risk is a skill published in the GitHub repository seandavi/scriptorium (3 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 4,190 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apple-container
Apple's open-source container CLI to build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS — no Docker daemon required. Use when the user mentions the container CLI, "apple container", running or building containers on macOS without Docker/Podman, container run, container…
pdlc-feature
An automated workflow for taking a new software feature from a description or requirements document through requirements, design, testing, implementation, review, and release preparation. It keeps one feature ID across the documents and requires tests before implementation.
pdlc-implement
A guarded coding workflow that implements a feature from its design document and existing tests, then checks the result. It requires tests to be written first, following TDD (test-driven development).
pdlc-ui-design
A user-interface and user-experience design guide that turns an existing product requirements document into a page and interaction plan. A PRD is a document describing what a product or feature must do.
pdlc-standard
A manager for team standards stored under the project's standards directory, such as coding, API, or naming rules. It keeps one current document per topic and records changes in a separate change log.
pdlc-status
A read-only progress overview for projects using PDLC, a documented process for moving a feature through stages such as design, testing, implementation, and review. It reads saved state files and groups work as ongoing, complete, or invalid.