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/a554b554/reactant/proofreadnpx skills add a554b554/Reactant --skill proofreadgit clone --depth 1 https://github.com/a554b554/ReactantWhat 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.00013 | $0.00499 |
| Opus 5 | $0.00006 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
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 2d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proofread
Fix grammar, spelling, and punctuation in the surrounding text.
Input
- File path: the file being processed.
- Surrounding text: the paragraph or block where the
<@proofread>tag appears. - Prompt (optional): narrow the scope (e.g., "only fix punctuation"). Default: fix all grammar issues.
Workflow
- Read the surrounding text. Read the full file if you need broader context.
- Fix grammar, spelling, and punctuation errors.
- Write the result back to the file: replace the surrounding text (including the
<@proofread>tag) with the corrected text.
Scope Modifiers
The surrounding text may contain scope modifier tags that control which regions you can edit.
- Protect
<< >>: Text inside<<and>>must NOT be modified, even if it contains errors. Remove the<<>>delimiters in the output, but keep the content unchanged. - Field
(( )): ONLY the text inside((and))may be modified. The surrounding text is context only — do not change it. Remove the(())delimiters in the output.
If neither modifier is present, the entire surrounding text is editable (default behavior).
Context References
The prompt may contain context references wrapped in double backticks ( ``). These point to external resources (file paths, section titles, etc.) that you should look up.
- As input: Read the referenced resource for additional context (e.g., to understand domain-specific terminology that should not be flagged). E.g.,
<@proofread: use terminology from ``glossary.md``>. - Resolve references relative to the source file's directory unless an absolute path is given.
- Remove the
Rules
- Do not change meaning, tone, or style.
- Only fix errors; do not rewrite.
- Respect scope modifiers: never edit protected regions, only edit field regions when present.
- Resolve all context references (
- The
<@proofread>tag and all modifier delimiters (<< >>,(( )),
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.
- 2d ago First seen · 46 lines · 13 tokens per session scan A 130bfb43b9b2
proofread is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 499 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…