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.
curl -O https://raw.githubusercontent.com/Alexander-M-Dickerson/ai-asset-pricing/main/.claude/skills/proofread/SKILL.mdgit clone --depth 1 https://github.com/Alexander-M-Dickerson/ai-asset-pricingWrote 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/alexander-m-dickerson/ai-asset-pricing/proofread)<a href="https://agentmods.dev/skills/alexander-m-dickerson/ai-asset-pricing/proofread"><img src="https://agentmods.dev/badge/skills/alexander-m-dickerson/ai-asset-pricing/proofread/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/alexander-m-dickerson/ai-asset-pricing/proofread"><img src="https://agentmods.dev/badge/skills/alexander-m-dickerson/ai-asset-pricing/proofread.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.00018 | $0.00854 |
| Opus 5 | $0.00009 | $0.00427 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
proofread 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proofread Skill
Scan for mechanical errors that /style-check does not cover: typos, LaTeX formatting issues, punctuation around equations, and spacing problems.
Examples
/proofread-- proofread the main .tex file/proofread introduction-- proofread only the introduction section/proofread path/to/file.tex-- proofread a specific file
Input
The user provides an optional section key, file path, or line range. If omitted, scan the project's main .tex file.
Workflow
Step 1: Extract Target Text
- If a section key is given, extract that section using
%% BEGIN/ENDmarkers - If a file path is given, read that file
- If no argument, read the main
.texfile - Note line numbers for all findings
Step 2: Spelling & Typo Scan
Search for common typos in prose and math-adjacent text:
- Misspelled words (e.g., "componet", "assigment", "misraking")
- Doubled words ("the the", "is is")
- Common academic misspellings ("accomodate", "occurence", "seperate", "consistant")
- Wrong word usage ("it's" for possessive, "affect/effect" confusion)
Step 3: LaTeX Formatting
Check for formatting issues:
\ref{eq:...}where\eqref{eq:...}should be used (equation references)- Missing non-breaking space:
Eq.\eqrefshould beEq.~\eqref - Same for:
Table\ref->Table~\ref,Figure\ref->Figure~\ref,Section\ref->Section~\ref Eq,~instead ofEq.~(comma vs period)- Inconsistent
\citetvs\citeusage - Unclosed braces or environments
Step 4: Spacing Issues
- Double spaces in prose (outside of LaTeX commands)
- Missing space after period (except in abbreviations like "e.g." or "i.e.")
- Tab/space mixing in indentation
- Trailing whitespace on lines
Step 5: Equation Punctuation
For displayed equations (\[...\], equation, align):
- Check trailing punctuation: equations ending sentences need a period, mid-sentence need a comma
- Consistent punctuation style across the paper
Step 6: Capitalization
- Section/subsection titles: check for consistent capitalization style
- "Theorem", "Lemma", "Proposition" capitalized when used as proper nouns with numbers
- "equation" lowercase when used generically, but "Eq." when followed by a reference
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 · 93 lines · 18 tokens per session scan A eeb1a004c858
proofread is a skill published in the GitHub repository Alexander-M-Dickerson/ai-asset-pricing (59 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 854 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.
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…
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…
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…