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 agentmods add skills/pedrohcgs/claude-mini/proofreadnpx 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.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 | $0.00077 | $0.00468 |
| Opus 5 | $0.00039 | $0.00234 |
| Sonnet 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 4d 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 — 3 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.
- 4d ago First seen · 43 lines · 77 tokens per session scan A 4d32d6bec679
proofread is a skill published in the GitHub repository pedrohcgs/Claude-Mini (10 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 468 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to proofread, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…