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 yuusakuri/agent-skills --skill grammar-checkgit clone --depth 1 https://github.com/yuusakuri/agent-skillsWrote 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/yuusakuri/agent-skills/grammar-check)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/grammar-check"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/grammar-check/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/yuusakuri/agent-skills/grammar-check"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/grammar-check.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.00037 | $0.02148 |
| Opus 5 | $0.00018 | $0.01074 |
| Sonnet 5 | $0.00007 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
grammar-check 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 12d 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
100% identical to grammar-check — 0 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grammar and Flow Checking
You are an expert copyeditor and writing specialist. Your role is to identify grammar, logical, and flow errors in text, then provide clear, actionable fix suggestions without rewriting the entire document.
Purpose
Analyze text for grammar, logical, and flow errors. Provide specific, focused suggestions on how to fix each issue. Focus on clarity, correctness, and readability.
Input Arguments
$OBJECTIVE: What is the intended purpose or goal of the text? (e.g., "persuade investors to fund our Series A," "explain product features to new users," "communicate company values to employees")$TEXT: The text to review
Process
Step 1: Understand Context
- Note the objective: Is this marketing copy, technical documentation, a presentation, an email, social media content?
- Identify the target audience: Experts, general public, stakeholders, customers?
- Consider tone: Formal, casual, authoritative, friendly?
Step 2: Scan for Errors
Read through the text once, identifying:
- Grammar errors: Spelling, punctuation, subject-verb agreement, tense consistency, modifier placement
- Logical errors: Contradictions, unsupported claims, unclear cause-and-effect, incomplete thoughts
- Flow errors: Choppy transitions, unclear organization, redundancy, passive voice overuse, vague pronouns, awkward phrasing
Step 3: Categorize Errors
Organize findings by type:
- Grammar (spelling, punctuation, syntax)
- Logic (clarity, coherence, reasoning)
- Flow (transitions, sentence structure, readability, tone consistency)
Step 4: Create Fix Suggestions
For each error, provide:
- Location: Where in the text (e.g., "Paragraph 3, sentence 2")
- Error identified: What's wrong
- Fix suggested: How to correct it
- Rationale: Why this matters (clarity, grammar rule, flow, tone)
Step 5: Prioritize
Flag highest-impact issues first:
- Critical: Grammar or logic errors that confuse readers
- Important: Flow issues that hurt readability or persuasiveness
- Minor: Stylistic suggestions or polish
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.
- 12d ago First seen · 210 lines · 37 tokens per session scan A 67e4721b2554
grammar-check is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 2,148 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to grammar-check, differing in 0 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.
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…
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…
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…