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 eugeniosegala/claude-connoisseur --skill proofreadgit clone --depth 1 https://github.com/eugeniosegala/claude-connoisseurWrote 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/eugeniosegala/claude-connoisseur/proofread)<a href="https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/proofread"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/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/eugeniosegala/claude-connoisseur/proofread"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/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.00017 | $0.00588 |
| Opus 5 | $0.00009 | $0.00294 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 11d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proofread
Fix grammar and improve writing in the specified files while keeping the author's original voice intact.
Files and instructions: $ARGUMENTS
Core principles to apply
- Fix grammar, spelling, and punctuation errors, but do not rewrite the author's style
- Always use British English (e.g. "colour", "organisation", "behaviour", "analyse")
- Never use dashes (em dashes, en dashes, or similar). Restructure into separate sentences or use commas, colons, or parentheses instead
- Keep the tone direct and concise, but never rude or disrespectful
- Do not over-polish. The writing should feel human and relatable, not robotic or corporate
- Preserve the author's sentence rhythm, word choices, and personality. If the original is casual, keep it casual. If it is blunt, keep it blunt
- Do not add filler words, hedging language, or unnecessary qualifiers
- Do not introduce AI-typical patterns: no "it's important to note", "in order to", "leverage", "utilise", "delve into", "it's worth mentioning", or similar
How to interpret arguments
The arguments are free-form and flexible. They may contain:
- File references of any type and in any format:
@README.md,docs/guide.md,CHANGELOG.md, CONTRIBUTING.md - Additional natural language instructions alongside file references, such as:
- "focus on the introduction section"
- "also fix the comments in the code"
- "keep technical terms as they are"
Parse the arguments to identify which files to proofread and what additional instructions apply. When additional instructions reference related files, follow those instructions to identify and process those files as well.
Examples
/proofread @README.md— proofread this file/proofread docs/guide.md, docs/setup.md— proofread multiple files/proofread @SKILL.md focus on the description sections only— proofread with targeted scope/proofread @blog-post.md keep all code examples exactly as they are— proofread with constraints
How to proceed
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.
- 11d ago First seen · 53 lines · 17 tokens per session scan A 2dac36c2a227
proofread is a skill published in the GitHub repository eugeniosegala/claude-connoisseur (9 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 588 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-31.
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…
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…
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…
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…