prose-style-rules

prose-style-rules is a skill for Claude Code from ihudak/ihudak-claude-plugins. It costs 112 tokens per session (1,791 once invoked), scanned A, original, MIT.

A set of writing rules for product documentation, planning documents, release notes, and similar content. It combines a general baseline with optional rules specific to an organization.

In plain words
What is it for?
Use it when creating or editing documentation, epics, product requirements, architecture documents, or release notes.
Why use it?
It gives writing agents consistent terminology, tone, grammar, and formatting while allowing a team to add its own standards.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the prose-style plugin — 1 skill, 3 commands, 2 agents shipped together

Good fit Use it when creating or editing documentation, epics, product requirements, architecture documents, or release notes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ihudak/ihudak-claude-plugins
Claude Code
/plugin install prose-style

Made for: Claude Code.

Or install prose-style, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 2 agents.

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 prose-style-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/prose-style-rules/github.svg)](https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/prose-style-rules)
Your own site
<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/prose-style-rules"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/prose-style-rules/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 prose-style-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/prose-style-rules"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/prose-style-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,791 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.00112 $0.01791
Opus 5 $0.00056 $0.00896
Sonnet 5 $0.00022 $0.00358
Haiku 4.5 $0.00011 $0.00179

Measured yesterday against content hash 3944181e83a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

prose-style-rules 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 yesterday.

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.

plugins/prose-style/skills/prose-style-rules/SKILL.md · 171 lines

How it starts

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

Prose style rules

This skill gives any writing agent the active prose style rules, so content comes out correctly styled instead of being corrected afterwards.

How to use

1. Resolve the active rule set

Same mechanism as prose-style-checker step 1, in short form. Every miss is a silent fall-through — never an error, never a prompt.

Baseline (always read):

${CLAUDE_PLUGIN_ROOT}/references/

This is also the path /prose-style-refresh asks this skill to resolve on its behalf, because ${CLAUDE_PLUGIN_ROOT} does not expand in a slash-command body. When a caller asks for the baseline directory, hand back this expanded absolute path. It is read-only: nothing ever writes into it, because a plugin update replaces it.

Overlay (read the first that resolves, then stop):

  1. <repo-root>/.prose-style/rules/ — where <repo-root> is git rev-parse --show-toplevel for the content being written, falling back to the working directory's repository, falling back to no overlay.
  2. $PROSE_STYLE_PATH — an absolute path to a rules directory.
  3. Nothing — the baseline alone.

A candidate resolves only when it is a readable directory holding at least one .md file.

2. Merge

The overlay augments and overrides the baseline, per file name. Both are in force; on any conflict about the same term or rule, the overlay wins. A term listed under an overlay's ## Allowed heading is not a violation. An overlay file whose first line is <!-- prose-style: replace --> replaces the same-named baseline file outright. An overlay file with a name no baseline file uses is an additional rule source.

3. Write

Apply the rules below while writing. The reference docs carry the full tables and examples; this checklist is the subset that changes the most sentences.

When the overlay and this checklist disagree, the overlay wins. This checklist restates the baseline, which an organization's overlay is entitled to override.


Quick checklist (apply while writing)

Read the full file on GitHub · 171 lines

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. yesterday Changed 3944181e83a4
  2. 5d ago First seen · 171 lines · 112 tokens per session scan A a227332dab99

Subscribe to this mod's changes

prose-style-rules is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 1,791 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-09-05.

Related

Other skills, from other repositories

dummy-dataset

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.

phuryn/pm-skills · 48 tokens

stakeholder-map

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

phuryn/pm-skills · 47 tokens

competitive-battlecard

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.

phuryn/pm-skills · 52 tokens

memory

Recall applicable reviewed topic pages or maintain them through separately budgeted mining, learning and curation. Triggers: "memory", "recall prior work", "mine and learn", "curate memory", "qualify or retire a lesson".

boshu2/agentops · 51 tokens

sheet-music-publisher

Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.

bitwize-music-studio/claude-ai-music-skills · 36 tokens

bun-test-mocking

Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.

secondsky/claude-skills · 25 tokens