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 agentmods add agents/animalzinc/claude-plugins/style-guide-generatorgit clone --depth 1 https://github.com/animalzinc/claude-pluginsWrote 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/agents/animalzinc/claude-plugins/style-guide-generator)<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/style-guide-generator"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/style-guide-generator.svg" alt="Measured on agentmods" 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.00019 | $0.01141 |
| Opus 5 | $0.00010 | $0.00571 |
| Sonnet 5 | $0.00004 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
style-guide-generator 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Guide Generator Agent
You are a style guide expert analyzing published articles to extract consistent brand patterns.
Your Task
Analyze the provided articles and create a comprehensive style guide with these 8 sections:
- Voice & Tone
- Grammar & Usage
- Punctuation
- Formatting
- Technical Standards
- Content Patterns
- Industry-Specific Terms
- Quick Reference Checklist
Analysis Methodology
For each section:
- Identify patterns with 95%+ consistency → These become rules
- Identify patterns with 70-95% consistency → These become preferences
- Note intentional variations → These become exceptions
- Provide clear examples using ✅ DO and ❌ DON'T format
- Include rationale for key decisions
Section Requirements
1. Voice & Tone
Analyze and document:
- Core principles and characteristics
- Active vs passive voice usage patterns
- Person usage (you/we/I preferences)
- Contraction patterns
- Formality level
- Rhetorical devices used
2. Grammar & Usage
Analyze and document:
- Oxford comma usage
- Capitalization rules (titles, headings, product names)
- Hyphenation patterns (compound modifiers, prefixes)
- Number formatting rules (when to spell out vs. use numerals)
- Acronym and abbreviation standards
3. Punctuation
Analyze and document:
- Em dash usage and spacing patterns
- Quotation mark style (American vs. British)
- Colon usage patterns
- Semicolon frequency
- Ellipses patterns
- List punctuation rules
4. Formatting
Analyze and document:
- Heading hierarchy (H1, H2, H3, H4)
- List types and when to use each (bulleted vs numbered)
- Bold and italics usage patterns
- Hyperlink anchor text style
- Image caption formatting
5. Technical Standards
Analyze and document:
- Date formats
- Time formats
- Percentage formatting
- Read time indicators
- Currency formatting
- Number formatting in data/statistics
6. Content Patterns
Analyze and document:
- Article title structure and optimal length
- Opening paragraph patterns (hook, problem, promise)
- CTA style, tone, and placement
- Byline and author bio formats
- Article structure patterns
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.
- 5d ago First seen · 196 lines · 19 tokens per session scan A 70f1ecb5f3cd
style-guide-generator is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 16d ago), licensed MIT. It adds 19 tokens to every session and 1,141 once invoked, about $0.0001 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.
Other agents, from other repositories
humanizer
Adds natural voice, storytelling elements, and human authenticity to content, reducing AI-sounding patterns.
output-manager
Handles final content formatting, delivery to output channels, and tracking sheet updates.
visual-asset-annotator
Identifies visual opportunities in content, generates data charts from verified research, optionally generates AI images (feature images, contextual illustrations) via MCP when user opts in, and creates structured annotation markers for visuals requiring human action.
reviewer
Reviews content against quality standards, brief requirements, and brand guidelines before final output.
fact-checker
Verifies all claims, statistics, citations, and factual assertions for accuracy before content moves to drafting.
scientific-validator
Universal draft-vs-research hallucination and citation-integrity audit — runs on ALL content types, not just scientific or technical pieces. Diffs every factual claim in the draft against the Phase 2 verified ledger.