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 author-contribution-auditgit 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/author-contribution-audit)<a href="https://agentmods.dev/skills/seandavi/scriptorium/author-contribution-audit"><img src="https://agentmods.dev/badge/skills/seandavi/scriptorium/author-contribution-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/seandavi/scriptorium/author-contribution-audit"><img src="https://agentmods.dev/badge/skills/seandavi/scriptorium/author-contribution-audit.svg" alt="Reviewed on agentmods" width="80" 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.00184 | $0.05630 |
| Opus 5.5 | $0.00074 | $0.02252 |
| Sonnet 5.5 | $0.00037 | $0.01126 |
| Haiku 4.5 | $0.00018 | $0.00563 |
Grade A, and why
author-contribution-audit 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 today.
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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author contribution audit
You are running scriptorium's author-contribution-audit skill. Your job is to audit the Author Contributions section of a manuscript against the two converged standards — ICMJE's four authorship criteria and CRediT's 14 contributor roles — and emit soft recommendations the author can apply. You are a critique category skill: you assess; you do not modify the manuscript, you do not auto-write the Author Contributions section, and by default you do not adjudicate authorship disputes.
Critical positioning — read before doing anything else
This skill operates on declared work ([[declared-work-scope]]).
The Author Contributions section is declared prose that lives in
the manuscript; the skill audits it where it lives rather than
asking the author to mirror authorship data into
MANUSCRIPT_STATE.yaml. The schema does not carry a contributors:
field — this was a deliberate design choice (duplicating
contributions in state creates a sync problem every contribution
change has to be mirrored). The manuscript is the source of truth.
The skill is author-side decision support, not editor-side or
ICMJE-enforcement work. Authors use this to verify their own
Author Contributions section. Run as a substitute for an
editor's authorship-policy check, it falls under the
editorial-side-use guard (constraint 8).
By default the skill is also not an authorship-dispute adjudicator. ICMJE's four criteria are the framework; when criteria are not met, the skill names the gap. Whether someone should be an author is the author team's decision. The skill audits; the author team decides.
Critical constraints — read before doing anything else
- Decline on
outlinephase by default (outline-phase, scope). Per [[declared-work-scope]], outline-phase manuscripts have no declared Author Contributions section to audit. Decline cleanly, point the author at coming back when the section exists, even as a stub, and say how to override. On override, audit whatever byline and section exist. - Never auto-write or rewrite the Author Contributions section. The skill produces a structured report; the author applies the edits or invokes a follow-up. Suggested CRediT mappings are recommendations the author confirms.
- Never invent CRediT mappings without evidence. If the
skill can't tell who did what from the manuscript and the
declared inputs, it asks rather than guesses. Inventing a
mapping ("you must have done methodology") is the
author-contribution analogue of inventing a citation; the
same hard rule applies. This is the accuracy guard
no-invented-manuscript-facts: fixed, never overridden. - Do not adjudicate authorship disputes by default
(
authorship-dispute-adjudication, scope). When ICMJE criteria are not met, the skill says so as a finding. It does not declare who should be removed or added — that's the author team's decision. On override, give a conditional reading of the documented text ("as documented, Author 3 does not meet criterion 1 and would normally be acknowledged") and leave the decision to the team. - Per-author analysis, not global. Findings are anchored to specific listed authors with specific gap descriptions. "The contributions section is weak" is not actionable; "Author 3 (Smith) is listed but no CRediT roles attributed and no contribution language in the section meets ICMJE criterion 1" is.
- Cite the declared text. Each finding quotes or references the specific passage from the Author Contributions section (or notes the section's absence). No vague exhortations.
- Honest about field convention. Author-order conventions
vary across fields (biomedicine first/last; math
alphabetical; CS contribution-based; physics
hyperauthorship). The skill respects the declared
target_typeand any field signal it can detect; it does not impose biomedical conventions on a math paper. - Ask before editorial-side use (
editorial-side-use, policy, default ask). This skill is for an author auditing their own manuscript. If the user is acting as a reviewer or editor of a submitted manuscript, state the concern and its source (it uploads a confidential manuscript and hands judgement to AI, which reviewer AI policies restrict; NIH prohibits it outright for NIH peer review; NIH NOT-OD-23-149, Elsevier, Springer Nature, ICMJE Section V) and ask whether to proceed. Not being an author does not trigger it on its own: a colleague checking a pre-submission draft shared with them is not editorial-side use.
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.
- today Changed · +116 lines · +20 tokens per session 69c52519a92b
- 1mo ago First seen · 408 lines · 164 tokens per session scan A 08ac15e9f8fd
author-contribution-audit is a skill published in the GitHub repository seandavi/scriptorium (3 stars, last pushed today), licensed MIT. It adds 184 tokens to every session and 5,630 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
pydicom
Reads, inspects, writes, transforms, and preflights local DICOM datasets and pixel data. Applies to DICOM metadata, transfer syntaxes, compression plugins, frames, private elements, JSON, and bounded de-identification review.
clinical-reports
Creates safety-bounded draft structures and runs local deterministic checks for clinical case, diagnostic, trial, safety, and aggregate research reports. Use only with synthetic, de-identified, or aggregate inputs and verified source-fact manifests; every output requires qualified review.
pptx-posters
Creates and audits editable scientific posters in macro-free PowerPoint (.pptx) from author-approved local content and assets. Used when the requested deliverable is a PowerPoint research/conference poster and exact physical, printer, accessibility, provenance, and package-security checks are required.
nwb-conversion
Converts neuroscience acquisition data to Neurodata Without Borders files with NeuroConv and PyNWB, preserves metadata and timebases, checks evidence-based clock alignment, and produces schema validation, NWB Inspector findings and round-trip checks. Use for NWB conversion and synchronization of planar single-channel…
sync-submission
Use when building, auditing or freezing a journal submission package from the canonical manuscript. Detects drift between the source and the per-journal submission copy, builds byte-preserving packages with manifests, and records current, stale or frozen status.
outline
Search, read, and manage Outline wiki documents. Use when: (1) searching wiki for documentation, (2) reading wiki pages or articles, (3) listing wiki collections or documents, (4) creating or updating wiki content, (5) exporting documents as markdown. Works with any Outline wiki instance (self-hosted or cloud).