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/flukeatzerocool/infobroker/proofreadingnpx skills add flukeatzerocool/infobroker --skill proofreadinggit clone --depth 1 https://github.com/flukeatzerocool/infobrokerWrote 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/flukeatzerocool/infobroker/proofreading)<a href="https://agentmods.dev/skills/flukeatzerocool/infobroker/proofreading"><img src="https://agentmods.dev/badge/skills/flukeatzerocool/infobroker/proofreading.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.00050 | $0.00757 |
| Opus 5 | $0.00025 | $0.00378 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
proofreading 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proofreading
When NOT to Use
- For creative writing where intentional rule-breaking is part of the voice.
- When the user wants a full rewrite rather than corrections.
Workflow
-
Grammar check. Fix subject-verb agreement, tense errors, dangling modifiers, fragments, and run-on sentences.
-
Spelling and word choice. Catch misspellings, homophones, and words used in the wrong context. Verify domain terms.
-
Punctuation. Review commas, semicolons, colons, dashes, hyphens, apostrophes, and quotation marks according to the style guide.
-
Style and consistency. Enforce heading capitalization, number formatting, abbreviations, passive voice, and consistent terminology. Verify the document conforms to any design philosophy or principles it declares (e.g., simplicity, no jargon, beginner-friendly). Flag deviations from that philosophy.
-
Clarity and readability. Flag long sentences, dense paragraphs, and jargon. Provide a readability score if useful.
-
Tone check. Ensure the tone matches the user's intent. Flag tonal shifts.
Output Format
Provide the corrected text and an annotated list of changes with original,
correction, and reason. Number each correction PR-<n> so it can be
referenced downstream:
1. PR-1 [location]: "original" → "correction" — [reason].
2. PR-2 [location]: "original" → "correction" — [reason].
Output Contract
Always produce a searchable one-line status:
proofread passed. [scope] — N corrections
The token is grep-able by build-review (as an Evidence: source) and
after-action-report (follow-through register).
Edit audit trail
Proofreading edits the file. Treat each correction as rollback-cost 1 (git-reversible): every applied edit must be individually revertible. When run inside a build, emit an evidence line for the pass:
Evidence: proofread passed. <scope> — N corrections applied.
If any correction is reverted, record the revert and its reason in the change list rather than silently dropping it.
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 · 102 lines · 50 tokens per session scan A 034085d2c834
proofreading is a skill published in the GitHub repository flukeatzerocool/infobroker (0 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 757 once invoked, about $0.0003 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…