style-check

style-check is a skill for Claude Code, Codex from reem-sab/tech-writer-prompts. It costs 110 tokens per session (779 once invoked), scanned A, original, MIT.

A style-guide checker for drafts that reports specific violations instead of rewriting the text. It gives quoted passages, the relevant rule, and a small suggested fix.

In plain words
What is it for?
Checking a draft against a prose guide or list of rules before a human edits it.
Why use it?
It helps authors find style-guide problems while keeping their wording and voice under their control. It flags only rules that the supplied guide actually covers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Checking a draft against a prose guide or list of rules before a human edits it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reem-sab/tech-writer-prompts/style-check
Install

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.

Any agent
npx skills add reem-sab/tech-writer-prompts --skill style-check
Clone the repo
git clone --depth 1 https://github.com/reem-sab/tech-writer-prompts

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for style-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/style-check/github.svg)](https://agentmods.dev/skills/reem-sab/tech-writer-prompts/style-check)
Your own site
<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/style-check"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/style-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.

agentmods 80×15 button for style-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/style-check"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/style-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 779 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.00779
Opus 5 $0.00055 $0.00390
Sonnet 5 $0.00022 $0.00156
Haiku 4.5 $0.00011 $0.00078

Measured 12d ago against content hash 31b7235a266f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

style-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.

prompts/style-check/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Style Check

Checks a draft against a style guide and reports violations as a numbered, diff-style list, giving the quoted span, the rule violated, and a minimal fix, without rewriting the piece. Run it before a human edit, not instead of one: the output is something an author reviews and applies themselves, which keeps their voice intact.

Inputs

  • {{DRAFT}}: The draft text to check.
  • {{STYLE_GUIDE}}: The style guide rules to apply (prose, a list of rules, or both).

How to apply

Substitute each {{PLACEHOLDER}} above with the user's actual content, then follow the prompt below exactly — including its output format and its stated limits.


You are checking DRAFT against STYLE_GUIDE. You are not an editor rewriting the piece — you are a linter reporting violations for the author to fix themselves. The author's voice, sentence rhythm, and word choices that aren't covered by STYLE_GUIDE are not your concern and must not change.

Rules

  • Only flag things STYLE_GUIDE actually says something about. If STYLE_GUIDE doesn't mention passive voice, don't flag passive voice, even if you personally would.
  • Quote the smallest span of text that contains the violation — a phrase or clause, not the whole paragraph it's in.
  • Propose the smallest possible fix that resolves the violation — a word swap or a small rephrase, not a rewritten sentence. If the smallest fix would require rewriting the whole sentence to satisfy the rule, say so explicitly instead of doing it.
  • Never propose a fix for something STYLE_GUIDE doesn't cover, even to "improve" the writing. That's out of scope for this pass.
  • If DRAFT has zero violations, say so — don't invent minor nitpicks to have something to report.

Output format

A numbered list, one entry per violation, in the order they appear in DRAFT:

N. Found: "<exact quoted span from DRAFT>"
   Rule: <the specific STYLE_GUIDE rule this violates, quoted or closely
   paraphrased>
   Fix: "<the smallest edit that resolves it>" (or: "Requires a full
   sentence rewrite to satisfy this rule — flagging for the author rather
   than rewriting.")

Read the full file on GitHub · 83 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 12d ago First seen · 83 lines · 110 tokens per session scan A 31b7235a266f

Subscribe to this mod's changes

style-check is a skill published in the GitHub repository reem-sab/tech-writer-prompts (4 stars, last pushed 13d ago), licensed MIT. It adds 110 tokens to every session and 779 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens