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 yegor256/critic --skill proofread-subtitlesgit clone --depth 1 https://github.com/yegor256/criticWrote 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/yegor256/critic/proofread-subtitles)<a href="https://agentmods.dev/skills/yegor256/critic/proofread-subtitles"><img src="https://agentmods.dev/badge/skills/yegor256/critic/proofread-subtitles/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/yegor256/critic/proofread-subtitles"><img src="https://agentmods.dev/badge/skills/yegor256/critic/proofread-subtitles.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.00034 | $0.00505 |
| Opus 5 | $0.00017 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
proofread-subtitles 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 10d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference
Ask author for domain-specific terms engine likely misrenders. Use that list as primary reference for errors. Proceed without list when author declines. Flag uncertain cues by number instead.
Structure
Keep timestamps, cue numbers, and blank line between cues unchanged. Keep each cue's boundaries exactly as in source. Break any line over 42 characters into two within same cue. Split at clause boundary, comma, or conjunction. Allow at most two text lines per cue. Shorten wording rather than add third line.
Punctuation
Add punctuation where spoken phrasing requires it. Follow source language's rules. Capitalize first word of every sentence and every proper noun. End every sentence with terminal mark.
Corrections
Fix obvious homophone and word misrecognitions when context is unambiguous.
Preserve computer jargon in its conventional form.
Use API, CLI, Git, Docker, JSON, HTTP, and Kubernetes as written.
Fix typos and spacing errors without rewording sentence.
Russian
In Russian subtitles, write computer terms in English.
Follow conventions of Russian tech speech.
Write pull request instead of пулл реквест.
Keep transliterations already standard in Russian.
Preserve
Preserve speaker's word choice and phrasing.
Keep filler words like uh, um, well, ну, and вот.
Delete them only when author requests filler-free transcript.
Omit speaker labels and sound descriptions.
Add bracketed annotations only where source already uses them.
Preserve file's existing encoding and line endings.
Uncertain
Leave original when unsure change preserves meaning. Flag cue number instead.
Output
Write output to sibling file <original>-corrected.srt.
Keep source file intact.
Verify cue count matches source.
Verify every cue number and timestamp matches too.
Report short categorized summary of changes at end.
Example
Correct this raw cue.
1
00:00:01,000 --> 00:00:03,000
lets push this to git hub tomorrow
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.
- 10d ago First seen · 84 lines · 34 tokens per session scan A ed00b7e6c34e
proofread-subtitles is a skill published in the GitHub repository yegor256/critic (4 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 505 once invoked, about $0.0002 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
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…