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.
/plugin marketplace add animalzinc/claude-plugins/plugin install blog-style-guide-creatorWrote 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/style-check)<a href="https://agentmods.dev/commands/animalzinc/claude-plugins/style-check"><img src="https://agentmods.dev/badge/commands/animalzinc/claude-plugins/style-check.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.00012 | $0.01643 |
| Opus 5 | $0.00006 | $0.00822 |
| Sonnet 5 | $0.00002 | $0.00329 |
| Haiku 4.5 | $0.00001 | $0.00164 |
Grade A, and why
style-check 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Check: Multi-Agent Article Review
Review the article at $2 against the $1 brand style guide using 8 specialized agents running in parallel.
Step 1: Validate Inputs
Before proceeding:
- Verify style guide exists at
brands/$1/style-guide.md- If missing: Error and suggest running
/generate-style-guide $1 [source]
- If missing: Error and suggest running
- Verify article exists at $2
- If missing: Error with clear message
- Check for
--auto-applyflag (determines whether to apply corrections automatically) - Check for
--dry-runflag (shows what would be changed without modifying files) - Note:
--dry-runtakes precedence over--auto-applyif both are specified
Step 2: Read Required Files
Read the following files:
- Article to review: $2
- Brand style guide:
brands/$1/style-guide.md - All 8 agent prompts from
agents/:- voice-tone-agent.md
- grammar-usage-agent.md
- punctuation-agent.md
- formatting-agent.md
- technical-standards-agent.md
- content-patterns-agent.md
- industry-terms-agent.md
- quick-reference-agent.md
Step 3: Launch 8 Specialized Agents in Parallel
CRITICAL: Use Task tool to launch ALL 8 agents simultaneously in a SINGLE message.
Each agent should receive:
- The agent prompt from
agents/[agent-name].md - The complete article content from $2
- The relevant section(s) from
brands/$1/style-guide.md
Launch these 8 agents in parallel:
- Agent 1 - Voice & Tone: Review against Section 1 of style guide
- Agent 2 - Grammar & Usage: Review against Section 2 of style guide
- Agent 3 - Punctuation: Review against Section 3 of style guide
- Agent 4 - Formatting: Review against Section 4 of style guide
- Agent 5 - Technical Standards: Review against Section 5 of style guide
- Agent 6 - Content Patterns: Review against Section 6 of style guide
- Agent 7 - Industry Terms: Review against Section 7 of style guide
- Agent 8 - Quick Reference: Final comprehensive check against Section 8
Each agent must return:
- List of violations with line numbers
- Specific corrections for each issue
- Citation of relevant style guide rules
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 · 225 lines · 0 tokens per session scan A bff6083df2c3
style-check is a command published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 17d ago), licensed MIT. It adds 12 tokens to every session and 1,643 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 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.