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 pedrohcgs/Claude-Mini --skill proofreadgit clone --depth 1 https://github.com/pedrohcgs/Claude-MiniWrote 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/pedrohcgs/claude-mini/proofread)<a href="https://agentmods.dev/skills/pedrohcgs/claude-mini/proofread"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-mini/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/pedrohcgs/claude-mini/proofread"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-mini/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.00077 | $0.00468 |
| Opus 5.5 | $0.00031 | $0.00187 |
| Sonnet 5.5 | $0.00015 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
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 1mo 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.
This is a copy
92% identical to proofread — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Proofread Lecture Files
Run the mandatory proofreading protocol on lecture files. This produces a report of all issues found WITHOUT editing any source files.
Steps
-
Identify files to review:
- If
$ARGUMENTSis a specific filename: review that file only - If
$ARGUMENTSis "all": review all lecture files inSlides/andQuarto/
- If
-
For each file, launch the proofreader agent that checks for:
GRAMMAR: Subject-verb agreement, articles (a/an/the), prepositions, tense consistency TYPOS: Misspellings, search-and-replace artifacts, duplicated words OVERFLOW: Overfull hbox (LaTeX), content exceeding slide boundaries (Quarto) CONSISTENCY: Citation format, notation, terminology ACADEMIC QUALITY: Informal language, missing words, awkward constructions
-
Produce a detailed report for each file listing every finding with:
- Location (line number or slide title)
- Current text (what's wrong)
- Proposed fix (what it should be)
- Category and severity
-
Save each report to
quality_reports/:- For
.texfiles:quality_reports/FILENAME_report.md - For
.qmdfiles:quality_reports/FILENAME_qmd_report.md
- For
-
IMPORTANT: Do NOT edit any source files. Only produce the report. Fixes are applied separately after user review.
-
Present summary to the user:
- Total issues found per file
- Breakdown by category
- Most critical issues highlighted
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.
- 1mo ago First seen · 43 lines · 77 tokens per session scan A 4d32d6bec679
proofread is a skill published in the GitHub repository pedrohcgs/Claude-Mini (11 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 468 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to proofread, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.