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.
git 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/commands/animalzinc/claude-plugins/generate-style-guide)<a href="https://agentmods.dev/commands/animalzinc/claude-plugins/generate-style-guide"><img src="https://agentmods.dev/badge/commands/animalzinc/claude-plugins/generate-style-guide.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.00009 | $0.01316 |
| Opus 5 | $0.00005 | $0.00658 |
| Sonnet 5 | $0.00002 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
generate-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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Style Guide for Brand
Generate a comprehensive house style guide for $1 based on sample articles.
Step 1: Collect Sample Articles
Users can combine any of these input methods:
Directory of local files
- If a directory path is provided, read all markdown/text files (*.md, *.txt)
- Gives full control over which articles to analyze
URLs pasted directly
- If URLs are provided, use WebFetch to retrieve each article
- URLs can be space-separated or on separate lines
- CRITICAL: Use this exact WebFetch prompt: "Extract the COMPLETE article content verbatim as markdown. Include the full title, all body paragraphs, all headings and subheadings, all lists, all quotes, and any author/date metadata. Preserve all formatting: bold, italics, hyperlinks (as markdown links), code blocks, and block quotes. Do NOT summarize or paraphrase. Return the entire article exactly as written."
- Save fetched articles to
brands/$1/source-articles/
Blog URL with guidance
- If a blog URL is provided, attempt to discover and fetch articles
- User can include guidance like "only articles from 2024 or later" or "focus on technical content"
- Follow user's guidance when selecting which articles to fetch
- CRITICAL: When fetching each discovered article, use this exact WebFetch prompt: "Extract the COMPLETE article content verbatim as markdown. Include the full title, all body paragraphs, all headings and subheadings, all lists, all quotes, and any author/date metadata. Preserve all formatting: bold, italics, hyperlinks (as markdown links), code blocks, and block quotes. Do NOT summarize or paraphrase. Return the entire article exactly as written."
Combining inputs
- All methods can be combined in a single command
- Example: local directory + a few extra URLs + guidance for additional discovery
Step 2: Validate Inputs
Before proceeding:
- Confirm at least 5 articles are available for analysis
- If 5-9 articles: Proceed, but note "10-15 articles recommended for best results"
- If <5 articles: Warn that results may be unreliable, ask user to confirm
- Create brand directory if it doesn't exist:
brands/$1/ - Create subdirectories:
brands/$1/source-articles/,brands/$1/articles/original/,brands/$1/articles/edited/
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.
- 7d ago First seen · 144 lines · 0 tokens per session scan A f59be72b402a
generate-style-guide is a command published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 17d ago), licensed MIT. It adds 9 tokens to every session and 1,316 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.
Other commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
content-brief
Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.
publish
Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.