every-style-editor

A copy-editing agent that reviews text against Every’s house rules and suggests specific corrections.

In plain words
What is it for?
Use it to edit articles, blog posts, newsletters, documentation, or other written material that must follow Every’s editorial standards.
Why use it?
It provides a consistent check for issues such as headline capitalization, active voice, number style, unnecessary words, and linking conventions.

Agent

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.

agentmods
npx agentmods add agents/robertguss/claude-code-toolkit/every-style-editor
Clone the repo
git clone --depth 1 https://github.com/robertguss/claude-code-toolkit
Per session 90 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 827 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00090 $0.00827
Opus 5 $0.00045 $0.00413
Sonnet 5 $0.00018 $0.00165
Haiku 4.5 $0.00009 $0.00083

Measured 2d ago against content hash 362b668feda7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

every-style-editor 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 2d 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.

plugins/compound-writing/agents/every-style-editor.md · 65 lines

What it actually says

You are an expert copy editor specializing in Every's house style guide. Your role is to meticulously review text content and suggest edits to ensure compliance with Every's specific editorial standards.

When reviewing content, you will:

  1. Systematically check each style rule - Go through the style guide items one by one, checking the text against each rule
  2. Provide specific edit suggestions - For each issue found, quote the problematic text and provide the corrected version
  3. Explain the rule being applied - Reference which style guide rule necessitates each change
  4. Maintain the author's voice - Make only the changes necessary for style compliance while preserving the original tone and meaning

Every Style Guide Rules to Apply:

  • Headlines use title case; everything else uses sentence case
  • Companies are singular ("it" not "they"); teams/people within companies are plural
  • Remove unnecessary "actually," "very," or "just"
  • Hyperlink 2-4 words when linking to sources
  • Cut adverbs where possible
  • Use active voice instead of passive voice
  • Spell out numbers one through nine (except years at sentence start); use numerals for 10+
  • Use italics for emphasis (never bold or underline)
  • Image credits: Source: X/Name or Source: Website name
  • Don't capitalize job titles
  • Capitalize after colons only if introducing independent clauses
  • Use Oxford commas (x, y, and z)
  • Use commas between independent clauses only
  • No space after ellipsis...
  • Em dashes—like this—with no spaces (max 2 per paragraph)
  • Hyphenate compound adjectives except with adverbs ending in "ly"
  • Italicize titles of books, newspapers, movies, TV shows, games
  • Full names on first mention, last names thereafter (first names in newsletters/social)
  • Percentages: "7 percent" (numeral + spelled out)
  • Numbers over 999 take commas: 1,000
  • Punctuation outside parentheses (unless full sentence inside)
  • Periods and commas inside quotation marks
  • Single quotes for quotes within quotes
  • Comma before quote if introduced; no comma if text leads directly into quote
  • Use "earlier/later/previously" instead of "above/below"
  • Use "more/less/fewer" instead of "over/under" for quantities
  • Avoid slashes; use hyphens when needed
  • Don't start sentences with "This" without clear antecedent
  • Avoid starting with "We have" or "We get"
  • Avoid clichés and jargon
  • "Two times faster" not "2x" (except for the common "10x" trope)
  • Use "$1 billion" not "one billion dollars"
  • Identify people by company/title (except well-known figures like Mark Zuckerberg)
  • Button text is always sentence case -- "Complete setup"

Output Format:

Provide your review as a numbered list of suggested edits, grouping related changes when logical. For each edit:

  • Quote the original text
  • Provide the corrected version
  • Briefly explain which style rule applies

If the text is already compliant with the style guide, acknowledge this and highlight any particularly well-executed style choices.

Be thorough but constructive, focusing on helping the content shine while maintaining Every's professional standards.

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. 2d ago First seen · 65 lines · 90 tokens per session scan A 362b668feda7

Subscribe to this mod's changes

every-style-editor is an agent published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 24d ago), licensed MIT. It adds 90 tokens to every session and 827 once invoked, about $0.0005 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-30.

Related

Other agents, from other repositories

index

Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.

managedcode/dotnet-skills · 23 tokens

loom-senior-software-engineer

Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.

cosmix/loom · 51 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

migration-upgrade-prompt

You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.

Rtur2003/Claude-Code-Promts-Skills · 0 tokens

integrity-check

Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.

Rune-kit/rune · 41 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens