What is submission-prep?

A checklist for preparing a research paper before sending it to a target academic journal, such as the Journal of Finance or Review of Financial Studies.

Use it to check a paper’s structure, abstract, page count, unfinished notes, required terminology, and other submission requirements for the chosen journal.

It catches missing sections, placeholders, unsuitable length, and journal-specific rule violations that can lead to rejection before the paper is reviewed.

How Alexander-M-Dickerson/ai-asset-pricing configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Alexander-M-Dickerson/ai-asset-pricing. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Alexander-M-Dickerson/ai-asset-pricing/main/.claude/skills/submission-prep/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Alexander-M-Dickerson/ai-asset-pricing

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep/github.svg)](https://agentmods.dev/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep)

Your own site

<a href="https://agentmods.dev/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep"><img src="https://agentmods.dev/badge/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep"><img src="https://agentmods.dev/badge/skills/alexander-m-dickerson/ai-asset-pricing/submission-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,200 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.01200
Opus 5	$0.00011	$0.00600
Sonnet 5	$0.00004	$0.00240
Haiku 4.5	$0.00002	$0.00120

Measured 12d ago against content hash 2960e1e0e001, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

submission-prep 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 12d 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.

.claude/skills/submission-prep/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Submission Prep Skill

Run a pre-submission checklist tailored to the target journal. Catches common rejection-worthy issues before you submit.

Examples

/submission-prep -- run full checklist (uses target journal from project's CLAUDE.md)
/submission-prep JF -- run checklist with JF-specific requirements
/submission-prep --strict -- flag warnings as failures

Workflow

Step 1: Load Target Journal

Read the project's CLAUDE.md for the target journal. If not specified, ask the user. Common targets: JF, RFS, JFE, RoF, JFQA, MS.

Step 2: Run Checks

2a. Document Structure

Abstract present and within word limit (100--150 words for JF/RFS/JFE)
Title length reasonable (<15 words recommended)
All expected body sections present (check project's CLAUDE.md for section list)
Page count within typical range (40--60 pages including appendices for top-3)

2b. Content Completeness

No [HUMAN EDIT REQUIRED] tags remaining in any .tex file
No TODO, FIXME, XXX comments in .tex
No \lipsum or placeholder text
No commented-out sections that should be removed or restored

2c. Terminology Compliance

Project-specific terminology used consistently (check project's CLAUDE.md)
No banned words from academic-writing.md Section 1

2d. Tables and Figures

All tables have self-contained captions (sample period, units, variable definitions)
All figures have self-contained captions with axis labels
All tables and figures are referenced in the text (\ref check)
Numbers use 2--3 significant digits (not computer output)
Tables use booktabs style (\toprule/\midrule/\bottomrule, no vertical lines)
Figures use vector format (PDF) where possible

2e. Bibliography

All \cite{} keys resolve to .bib entries
No unused .bib entries
No duplicate .bib entries
Consistent BibTeX format (all @article have journal, year, volume, pages)
Proper nouns protected in titles: {CAPM}, {U.S.}, {NYSE}, etc.

Read the full file on GitHub · 120 lines

Changes

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.

12d ago First seen · 120 lines · 22 tokens per session scan A 2960e1e0e001

Subscribe to this mod's changes

submission-prep is a skill published in the GitHub repository Alexander-M-Dickerson/ai-asset-pricing (59 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,200 once invoked, about $0.0001 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.

Research Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

ai-asset-pricing: Skill for Claude Code