update-style-guide

update-style-guide is a command for Claude Code from animalzinc/claude-plugins. It costs 9 tokens per session (1,174 once invoked), scanned A, original, MIT.

A command that adds patterns from new articles to an existing brand style guide. A style guide is a set of rules for writing consistently for a brand.

In plain words
What is it for?
Use it to compare at least three new Markdown articles with an existing guide, exclude duplicate source articles, and update the guide's rules and version.
Why use it?
It helps keep the guide current while distinguishing new patterns from rules that are contradicted, confirmed, duplicated, or missing.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Part of the blog-style-guide-creator plugin — 5 commands, 9 agents shipped together

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 commands/animalzinc/claude-plugins/update-style-guide
Clone the repo
git clone --depth 1 https://github.com/animalzinc/claude-plugins

Made for: Claude Code.

Or install blog-style-guide-creator, the plugin that ships this one along with the rest of its 5 commands, 9 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 update-style-guide

README.md
[![agentmods](https://agentmods.dev/badge/commands/animalzinc/claude-plugins/update-style-guide.svg)](https://agentmods.dev/commands/animalzinc/claude-plugins/update-style-guide)
Your own site
<a href="https://agentmods.dev/commands/animalzinc/claude-plugins/update-style-guide"><img src="https://agentmods.dev/badge/commands/animalzinc/claude-plugins/update-style-guide.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,174 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.1 $0.00009 $0.01174
Opus 5 $0.00005 $0.00587
Sonnet 5 $0.00002 $0.00235
Haiku 4.5 $0.00001 $0.00117

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

Security

Grade A, and why

update-style-guide 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 6d 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/blog-style-guide-creator/commands/update-style-guide.md · 162 lines

How it starts

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

Update Style Guide

Incrementally update the $1 style guide with patterns from new articles at $2.

Step 1: Validate Existing Style Guide

Before proceeding:

  • Verify style guide exists at brands/$1/style-guide.md
    • If missing: Error and suggest running /generate-style-guide $1 [source]
  • Read and parse existing style guide
  • Extract current rules, preferences, and exceptions from all 8 sections
  • Note current version number (e.g., "1.0", "1.1")

Step 2: Collect New Articles

  • Read all markdown files from $2
  • Verify at least 3 new articles provided
    • If fewer than 3: Warn that updates may be less reliable
  • Check articles aren't already in brands/$1/source-articles/ (avoid duplicates)
  • If duplicates found: Warn user and exclude duplicates from analysis

Step 3: Analyze New Patterns

Launch style guide generator agent (Opus model) with:

  • Existing style guide content
  • New article contents
  • Special instruction: "Compare new articles against existing rules. Identify:
    1. NEW patterns not covered by existing rules
    2. Patterns that CONTRADICT existing rules
    3. Patterns that CONFIRM existing rules (strengthen confidence)"

The agent should categorize findings:

  • New Rules: Patterns appearing in 95%+ of new articles that aren't in current guide
  • Rule Modifications: Existing rules that new articles consistently contradict
  • Confirmed Rules: Existing rules that new articles follow (no action needed)
  • Edge Cases: Unusual patterns that may warrant adding exceptions

Step 4: Generate Update Report

Create report showing proposed changes:

# Style Guide Update Report: $1

**Current Version:** [X.X]
**Proposed Version:** [X.Y]
**New Articles Analyzed:** [number]
**Date:** [current date]

---

## Proposed Changes

### New Rules to Add

**Section [X] - [Section Name]:**
- **New Rule:** [description]
  - **Evidence:** Found in [X]/[Y] new articles
  - **Example:** [example from articles]

### Rules to Modify

**Section [X] - [Section Name]:**
- **Current Rule:** [existing text]
- **Proposed Change:** [new text]
- **Reason:** New articles show [pattern] in [X]/[Y] cases

### Rules Confirmed (No Changes)

- Section 1: [X] rules confirmed
- Section 2: [X] rules confirmed
- ...

### Potential Exceptions to Add

- **Rule:** [existing rule]
- **Exception:** [new exception based on articles]
- **Example:** [example showing valid exception]

---

## Summary

- New rules to add: [X]
- Rules to modify: [X]
- Rules confirmed: [X]
- Exceptions to add: [X]

Read the full file on GitHub · 162 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. 6d ago First seen · 162 lines · 0 tokens per session scan A af12542fa339

Subscribe to this mod's changes

update-style-guide is a command published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 16d ago), licensed MIT. It adds 9 tokens to every session and 1,174 once invoked, about $0.0000 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.